Systems and Methods for Displaying Groups of Applications via Inputs Received at a Touch-Sensitive Secondary Display

ABSTRACT

Disclosed herein are systems and methods that enable users to customize operation of a touch-sensitive secondary display. An example method includes displaying, at the touch-sensitive secondary display, a system-level affordance for controlling a system-level feature and an affordance for causing display of representations of user-defined workspaces. Receiving a first input at the affordance for causing display of the representations the user-defined workspaces. In response to receiving the first input, displaying, at the touch-sensitive secondary display, a selectable user interface object corresponding to a first window from a first application and a second window from a second application. Receiving a selection, and in response to receiving the second input corresponding to selection of the selectable user interface object corresponding to the first window from the first application and the second window from the second application, displaying the first window from the first application and the second window from the second application.

TECHNICAL FIELD

This application is a continuation of U.S. patent application Ser. No.16/857,509, filed Apr. 24, 2020, which is a continuation of U.S. patentapplication Ser. No. 16/142,633, filed Sep. 26, 2018, now U.S. Pat. No.10,635,134, which claims priority to U.S. Provisional Application Ser.No. 62/670,529, filed May 11, 2018, each of which is hereby incorporatedby reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments relate to touch-sensitive secondary displaydevices and, more specifically, customizing display modes for atouch-sensitive secondary display.

BACKGROUND

Integrating touch-sensitive secondary displays into computing systemshas resulted in new ways for users to interact with these systems, andin particular, for the provision of affordances in the secondarydisplays that are selected dynamically based on context of anapplication displayed at a primary display of the computing system. Incertain instances, however, some users are unable to easily locatedesired affordances within the secondary display while using certainapplications. As such, there is a need for customization features thatallow users to easily switch between different display modes for thesecondary display and that also allows users to associate display modesfor the secondary display with different applications.

SUMMARY

The embodiments described herein address the above shortcomings byproviding devices and methods that allow users to easily switch betweendifferent display modes for the touch-sensitive secondary display, andby providing a management user interface that allows users to associatedisplay modes for the touch-sensitive secondary display with variousapplications. Such devices and methods also reduce the amount of modeswitching (e.g., moving one's hands between keyboard and mouse, and alsomoving one's eyes from keyboard to display) required of a user andthereby reduce the number of inputs required to located desiredaffordances (e.g., number of inputs required to select menu options isreduced, as explained in more detail below). Such devices and methodsalso make more relevant information available on a limited screen (e.g.,a touch-sensitive secondary display is used to provide affordances thata user and actually needs and these affordances are efficientlypresented using limited screen space). Such devices and methods alsoprovide improved man-machine interfaces, e.g., by providing emphasizingeffects to make information more discernable on a touch-sensitivesecondary display, by providing sustained interactions so thatsuccessive inputs from a user directed to either a touch-sensitivesecondary display or a primary display cause the device to provideoutputs which are then used to facilitate further inputs from the user(e.g., affordances are displayed at the touch-sensitive secondarydisplay that allow users to quickly preview how information will berendered on a primary display, by providing inputs at thetouch-sensitive secondary display, as discussed below), and by requiringfewer interactions from users to achieve desired results. In someinstances, the touch-sensitive secondary display is also referred toherein as a dynamic function row (and vice versa). For these reasons andthose discussed below, the devices and methods described herein reducepower usage and improve battery life of electronic devices.

In accordance with some embodiments, a method is performed at acomputing system with one or more processors, a first housing thatincludes a primary display, memory, and a second housing (that isdistinct from the first housing) at least partially containing atouch-sensitive secondary display that is distinct from the primarydisplay (as discussed below, the second housing and the touch-sensitivesecondary display may be components of any device that includes asmaller display than that of the primary display, e.g., thetouch-sensitive secondary display is part of a wearable computingdevice, such as a watch, or the touch-sensitive secondary display islocated above a physical keyboard in the second housing). The methodincludes: displaying, on the primary display, a first user interface fora first application, the first user interface being in focus on theprimary display. While the touch-sensitive secondary display isoperating in an adaptive display mode in which at least someapplication-specific user interface elements are adaptively selected fordisplay on a respective portion of the touch-sensitive secondary displaybased on a current state of the first user interface for theapplication, the method includes: displaying, on a respective portion ofthe touch-sensitive secondary display, a plurality ofapplication-specific user interface elements that are selected based onthe current state of the first user interface for the application; andreceiving a request to operate the touch-sensitive secondary display ina respective persistent display mode for the touch-sensitive secondarydisplay, the respective persistent display mode being distinct from theadaptive display mode. In response to receiving the request, the methodincludes: operating the touch-sensitive secondary display in therespective persistent display mode, including updating the respectiveportion of the touch-sensitive secondary display to display a fixed setof user interface elements associated with the respective persistentdisplay mode. After changing focus to a second user interface for asecond application, the method includes: displaying, on the primarydisplay, the second user interface for the second application; andmaintaining display, on the respective portion of the touch-sensitivesecondary display, of the fixed set of user interface elementsassociated with the respective persistent display mode.

In some instances, users of computing systems are unable to change thedisplay mode of a touch-sensitive secondary display from an adaptivedisplay mode to a persistent display mode. In the adaptive display mode,at least some application-specific user interface elements are selectedby the computing system and displayed on the touch-sensitive secondarydisplay based on a state of an application that is currently in focus,while in the persistent display mode a fixed set of user interfaceelements is continuously/persistently displayed on the touch-sensitivesecondary display and the fixed set continues to be displayed even asthe state of the application may change. Receiving a request from theuser to operate in the predefined persistent display mode provides theuser with a convenient way to quickly switch to the persistent displaymode. Providing this option to quickly switch between display modesenhances operability of the device and makes the human-machine interfacemore efficient (e.g., by allowing the users to easily customize theiruse of the touch-sensitive secondary display without having to wastetime manually searching for desired user interface elements that may bedifficult to locate or may be unavailable based on certain states of theapplication).

In accordance with some embodiments, a method is performed at acomputing system with one or more processors, a first housing thatincludes a primary display, memory, and a second housing (that isdistinct from the first housing) at least partially containing atouch-sensitive secondary display that is distinct from the primarydisplay (as discussed below, the second housing and the touch-sensitivesecondary display may be components of any device that includes asmaller display than that of the primary display, e.g., thetouch-sensitive secondary display is part of a wearable computingdevice, such as a watch, or the touch-sensitive secondary display islocated above a physical keyboard in the second housing). The methodincludes: displaying, on the primary display, a management userinterface for the touch-sensitive secondary display, the management userinterface including concurrently displayed representations of aplurality of applications, including a representation of a firstapplication that, before being displayed within the management userinterface, was associated with one or more display modes of a firstplurality of available display modes for the touch-sensitive secondarydisplay, and a representation of a second application that, before beingdisplayed within the management user interface, was associated with oneor more display modes of a second plurality of the available displaymodes for the touch-sensitive secondary display. The method alsoincludes: detecting, via the one or more input devices, one or moreinputs that correspond to a request to modify which of the availabledisplay modes is associated with the first application. In response todetecting the one or more inputs, the method includes: associating thefirst application with a first display mode of the available displaymodes; and updating the management user interface to indicate that thefirst application is associated with the first display mode of theavailable display modes for the touch-sensitive secondary display. Achange in focus at the primary display to a user interface associatedwith the first application causes the touch-sensitive secondary displayto begin operating in the first display mode.

In some instances, users of computing systems are unable to associateavailable display modes of a touch-sensitive secondary display withapplications displayed on a primary display. Providing a management userinterface on the primary display that allows a user to predefine anassociation between such display modes and applications enhancesoperability of the device and makes the human-machine interface moreefficient (e.g., by allowing the users to predefine an associationbetween a display mode and an application without wasting computingresources during the operation of the application, and thereby allowingusers to easily customize their use of the touch-sensitive secondarydisplay without having to waste time manually searching for desireddisplay mode features that may be difficult to locate).

In accordance with some embodiments, a computing system includes a firsthousing with a primary display unit configured to display userinterfaces, a second housing (that is distinct from the first housing)at least partially containing a touch-sensitive secondary display thatis distinct from the primary display and that is configured to receiveuser inputs and to display user interfaces, and a processing unit thatis in communication with the primary display unit and thetouch-sensitive secondary display unit. The processing unit isconfigured to: cause display, on the primary display, of a first userinterface for a first application, the first user interface being infocus on the primary display; while the touch-sensitive secondarydisplay is operating in an adaptive display mode in which at least someapplication-specific user interface elements are adaptively selected fordisplay on a respective portion of the touch-sensitive secondary displaybased on a current state of the first user interface for theapplication: cause display, on a respective portion of thetouch-sensitive secondary display, of a plurality ofapplication-specific user interface elements that are selected based onthe current state of the first user interface for the application; andreceive a request to operate the touch-sensitive secondary display in arespective persistent display mode for the touch-sensitive secondarydisplay, the respective persistent display mode being distinct from theadaptive display mode; in response to receiving the request: operate thetouch-sensitive secondary display in the respective persistent displaymode, including updating the respective portion of the touch-sensitivesecondary display to display a fixed set of user interface elementsassociated with the respective persistent display mode and afterchanging focus to a second user interface for a second application:cause display, on the primary display, of the second user interface forthe second application; and maintaining display, on the respectiveportion of the touch-sensitive secondary display, of the fixed set ofuser interface elements associated with the respective persistentdisplay mode.

In accordance with some embodiments, a computing system includes a firsthousing with a primary display unit configured to display userinterfaces, a second housing (that is distinct from the first housing)at least partially containing a touch-sensitive secondary display thatis distinct from the primary display and that is configured to receiveuser inputs and to display user interfaces, and a processing unit thatis in communication with the primary display unit and thetouch-sensitive secondary display unit. The processing unit isconfigured to: cause display, on the primary display, of a managementuser interface for the touch-sensitive secondary display, the managementuser interface including concurrently displayed representations of aplurality of applications, including a representation of a firstapplication that, before being displayed within the management userinterface, was associated with one or more display modes of a firstplurality of available display modes for the touch-sensitive secondarydisplay, and a representation of a second application that, before beingdisplayed within the management user interface, was associated with oneor more display modes of a second plurality of the available displaymodes for the touch-sensitive secondary display. The processing unit isalso configured to: detect, via the one or more input devices, one ormore inputs that correspond to a request to modify which of theavailable display modes is associated with the first application. Inresponse to detecting the one or more inputs, the processing unit isconfigured to: associate the first application with a first display modeof the available display modes; and update the management user interfaceto indicate that the first application is associated with the firstdisplay mode of the available display modes for the touch-sensitivesecondary display. A change in focus at the primary display to a userinterface associated with the first application causes the processingunit to begin operating the touch-sensitive secondary display in thefirst display mode.

In accordance with some embodiments, a computing system includes one ormore processors, a first housing with a primary display, a secondhousing at least partially containing a touch-sensitive secondarydisplay that is distinct from the primary display and optionallycontaining one or more sensors to detect intensity of contacts with thetouch-sensitive secondary surface, and memory storing one or moreprograms, the one or more programs configured for execution by the oneor more processors and the one or more programs include instructions forperforming or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, acomputer-readable storage medium has stored therein instructions that,when executed by the computing system, cause the computing system toperform or cause performance of the operations of any of the methodsdescribed herein. In accordance with some embodiments, a graphical userinterface on the primary display of the computing system is provided,and the graphical user interface includes one or more of the elementsdisplayed in any of the methods described herein, which are updated inresponse to inputs, as described in any of the methods described herein.In accordance with some embodiments, the computing system includes meansfor performing or causing performance of the operations of any of themethods described herein. In accordance with some embodiments, aninformation processing apparatus, for use in the computing system,includes means for performing or causing performance of the operationsof any of the methods described herein.

Thus, computing systems that include both primary and touch-sensitivesecondary displays are provided with faster, more efficient andusable/user-friendly methods and interfaces for allowing users tocustomize which affordances are displayed at touch-sensitive secondarydisplays and to customize associations between various display modes forthe touch-sensitive secondary display and different applications,thereby improving operability of the computing system by, e.g., allowingusers to have sustained interactions with the touch-sensitive secondarydisplay, without wasting time searching for affordances that may bedifficult to locate.

BRIEF DESCRIPTION OF DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is an illustrative diagram of a portable computing system (e.g.,a laptop computer), in accordance with some embodiments.

FIG. 1B is an illustrative diagram of a body portion of the portablecomputing system in FIG. 1A, in accordance with some embodiments.

FIG. 2A is an illustrative diagram of a first implementation of adesktop computing system, in accordance with some embodiments.

FIG. 2B is an illustrative diagram of a second implementation of adesktop computing system, in accordance with some embodiments.

FIG. 2C is an illustrative diagram of a third implementation of adesktop computing system, in accordance with some embodiments.

FIG. 2D is an illustrative diagram of a fourth implementation of adesktop computing system, in accordance with some embodiments.

FIG. 3A is a block diagram of an electronic device, in accordance withsome embodiments.

FIG. 3B is a block diagram of components for event handling of FIG. 3A,in accordance with some embodiments.

FIGS. 3C-3E illustrate examples of dynamic intensity thresholds inaccordance with some embodiments.

FIG. 4 is a block diagram of a peripheral electronic device, inaccordance with some embodiments.

FIGS. 5A-5AT are schematics of primary and secondary displays used toillustrate example user interfaces for allowing users to customizedisplay modes for touch-sensitive secondary displays, in accordance withsome embodiments.

FIGS. 6A-6D show a flowchart of a method of using customized displaymodes for touch-sensitive secondary displays, in accordance with someembodiments.

FIGS. 7A-7F show a flowchart of interacting with a management userinterface for touch-sensitive secondary displays, in accordance withsome embodiments.

FIG. 8 shows a flowchart of selecting a display mode in which to operatethe touch-sensitive secondary display, in accordance with someembodiments.

DESCRIPTION OF EMBODIMENTS

FIGS. 1A-1B, 2A-2D, 3A-3E, and 4 provide a description of exampledevices. FIGS. 5A-5AT are schematics of a display used to illustrateexample user interfaces for customizing display modes fortouch-sensitive secondary displays. FIGS. 6A-6D and 7A-7F are flowchartsof methods of using customized display modes for touch-sensitivesecondary displays and for interacting with a management user interfacefor touch-sensitive secondary displays, respectively. The userinterfaces in FIGS. 5A-5AT are used to illustrate the methods and/orprocesses in FIGS. 6A-6D and 7A-7F.

Example Devices and Systems

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the various described embodiments. However,it will be apparent to one of ordinary skill in the art that the variousdescribed embodiments may be practiced without these specific details.In other instances, well-known methods, procedures, components,circuits, and networks have not been described in detail so as not tounnecessarily obscure aspects of the embodiments.

It will also be understood that, although the terms first, second, etc.are, in some instances, used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first contactcould be termed a second contact, and, similarly, a second contact couldbe termed a first contact, without departing from the scope of thevarious described embodiments. The first contact and the second contactare both contacts, but they are not the same contact.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a”, “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

As used herein, the term “if” is, optionally, construed to mean “when”or “upon” or “in response to determining” or “in response to detecting,”depending on the context. Similarly, the phrase “if it is determined” or“if [a stated condition or event] is detected” is, optionally, construedto mean “upon determining” or “in response to determining” or “upondetecting [the stated condition or event]” or “in response to detecting[the stated condition or event],” depending on the context.

FIG. 1A is an illustrative diagram of a portable computing system 100,in accordance with some embodiments. Portable computing system 100 maybe, for example, a laptop computer, such as a MACBOOK® device, or anyother portable computing device. Portable computing system 100 includes:(A) a display portion 110 (also referred to herein as a first housing110 or housing 110) with a primary display 102; and (B) a body portion120 (also referred to as a second housing 120 or housing 120) with adynamic function row 104, a set of physical (i.e., movably actuated)keys 106, and a touchpad 108 partially contained within a same housing.In some embodiments, a biometric sensor 105 (e.g., a fingerprint sensor105) is also at least partially contained within the body portion 120,and can be positioned directly adjacent to the dynamic function row 104(as is depicted in FIGS. 5A-5AT. Display portion 110 is typicallymechanically, electrically, and communicatively coupled with bodyportion 120 of portable computing system 100. For example, portablecomputing system 100 may include a hinge, allowing display portion 110to be rotated relative to body portion 120. Portable computing system100 includes one or more processors and memory storing one or moreprograms for execution by the one or more processors to perform any ofthe embodiments described herein. In some embodiments, dynamic functionrow 104, which is described in more detail with reference to FIG. 1B, isa touch screen display using resistive sensing, acoustic sensing,capacitive sensing, optical sensing, infrared sensing, or the like todetect user touch inputs and selections. In some embodiments, primarydisplay 102 of display portion 110 is also a touch screen display.

FIG. 1B is an illustrative diagram of body portion 120 of portablecomputing system 100 in accordance with some embodiments. Body portion120 includes a set of physical keys 106 (also referred to herein as“physical keys 106” and “keyboard 106”), a dynamic function row 104, anda touchpad 108 partially contained within a same housing. In someembodiments, dynamic function row 104, which is a touch screen, replacesa function row of the set of physical keys 106 allowing the spaceconsumed by the set of physical keys 106 to be reduced, allowing for asmaller overall body portion 120 or allowing other portions, such astouchpad 108, to be larger. In some embodiments, dynamic function row104 is approximately 18 inches in length relative to a major dimensionof the set of physical keys 106. Although called a “row” for ease ofexplanation, in some other embodiments, the touch screen comprisingdynamic function row 104 in FIG. 1A may take any other form such as asquare, circle, a plurality of rows, column, a plurality of columns, aplurality of separate sectors, or the like. Although FIGS. 1A-1B showdynamic function row 104 replacing the function row of the set ofphysical keys 106, in some other embodiments, dynamic function row 104may additionally and/or alternatively replace a numpad section,editing/function section, or the like of the set of physical keys 106.

Each physical key of the set of physical keys 106 has at least oneassociated input. The input may be a printable character, non-printablecharacter, function, or other input. The input associated with aphysical key may be shown by a letter, word, symbol, or other indiciashown (e.g., printed) on the surface of the key in Latin script, Arabiccharacters, Chinese characters, or any other script. For example, theparticular physical key indicated at 138 is associated with alphabeticcharacter “z” as indicated by the letter z shown on the key. In anotherexample, a physical key labeled with the word “command” may beassociated with a command function. For example, the set of physicalkeys 106 is associated with a QWERTY, Dvorak, or other keyboard layoutswith alphanumeric, numeric, and/or editing/function sections (e.g.,standard, extended, or compact) according to ISO/IEC 9995, ANSI-INCITS154-1988, JIS X 6002-1980, or other similar standards.

A signal corresponding to an input associated with a physical key may bereceived by the processor of portable computing system 100 (or computingdevice 202 in FIGS. 2A-2D or peripheral keyboard 206 in FIGS. 2A-2B)when a key has been activated by a user. In an illustrative example,each key of the set of physical keys 106 includes two plates and aspring. A user may activate a key by pressing down on the key, whichcompresses the spring. When the spring is compressed, the two plates maycome into contact, allowing electric current to flow through theconnected plates. An input corresponding to the key may be provided to aprocessor in response to the flow of the current through the connectedplates. For example, in response to activation of one of the set of keys106 of peripheral keyboard 206 in FIG. 2C, an input corresponding to theactivated key is provided to computing device 202. It will be recognizedthat other systems for movably actuated keys could be used.

In some embodiments, dynamic function row 104 is a touch screen display(the dynamic function row is also referred to herein as atouch-sensitive secondary display 104) that displays one or moreuser-selectable symbols 142 (sometimes also herein called “userinterface elements,” “user interface components,” “affordances,”“buttons,” or “soft keys”). For example, dynamic function row 104replaces the function row keys on a typical keyboard. A user may selecta particular one of the one or more user-selectable symbols 142 bytouching a location on the touch screen display that corresponds to theparticular one of the one or more user-selectable symbols 142. Forexample, a user may select the user-selectable symbol indicated bymagnifying glass symbol 144 by tapping dynamic function row 104 suchthat the user's finger contacts dynamic function row 104 at the positionof the magnifying glass indicator 214. In some embodiments, a tapcontact or a tap gesture includes touch-down of a contact and lift-offof the contact within a predetermined amount of time (e.g., 250 ms orthe like). In some embodiments, the touch screen display of dynamicfunction row 104 is implemented using resistive sensing, acousticsensing, capacitive sensing, optical sensing, infrared sensing, or thelike to detect user inputs and selections.

When a user selects a particular one of the one or more user-selectablesymbols 142, a signal corresponding to the particular one of the one ormore user-selectable symbols 142 is generated by dynamic function row104. For example, when a user taps “esc” on dynamic function row 104,dynamic function row 104 transmits a signal indicating a user inputcorresponding to an escape function to the processor of portablecomputing system 100 (or computing device 202 in FIGS. 2A-2D).

In some embodiments, when a particular one of the one or moreuser-selectable symbols 142 is selected, dynamic function row 104transmits a signal corresponding to a position on the touch screendisplay where the particular one of the one or more user-selectablesymbols 142 is displayed, to the processor of portable computing system100 (or computing device 202 in FIGS. 2A-2D). For example, dynamicfunction row 104 may transmit a signal including a position value (0 to20) depending on the position on the touch screen display of theparticular one of the one or more user-selectable symbols 142 that wasselected. In the illustrative example of FIG. 1B, the “esc” symbol mayhave a position value of 0, magnifying glass symbol 144 may have aposition value of 16, and so on. A processor of portable computingsystem 100 (or computing device 202 in FIGS. 2A-2D) may receive thesignal indicating the position value of the selected user-selectablesymbol and interpret the position value using contextual information,such as an element of a graphical user interface displayed on primarydisplay 102 of display portion 110 (or peripheral display device 204,FIGS. 2A-2D) that is currently active or that has focus.

Each of the one or more user-selectable symbols 142 may include anindicator, such as a symbol (e.g., a magnifying glass symbol as shown at144), an abbreviated word (e.g., “esc”), an unabbreviated word, acharacter, an image, an animated image, a video, or the like. In someembodiments, a respective one of the one or more user-selectable symbols142 is capable of receiving user input(s).

An input may be associated with each of the one or more user-selectablesymbols 142. The input may be a function, character, numerical value,and the like. A respective one of the one or more user-selectablesymbols 142 may include an indicator that corresponds to the input forthe respective one of the one or more user-selectable symbols 142. Forexample, in FIG. 1B, the user-selectable symbol with the abbreviatedword “esc” indicates to the user that an escape function is associatedwith the user-selectable symbol. A function associated with the one ormore user-selectable symbols 142 may be activated when the user selectsa user-selectable symbol. For example, an escape function may beactivated when a user selects the user-selectable symbol with theindicator “esc.” Activation of the function may have different effectsdepending on the current state of portable computing system 100 (orcomputing device 202 in FIGS. 2A-2D). For example, when a dialog box isopen on primary display 102 of display portion 110 (or peripheraldisplay device 204, FIGS. 2A-2D), activating an escape function ondynamic function row 104 may close the dialog box. In another example,when a game application is being executed by a processor of portablecomputing system 100 (or computing device 202 in FIGS. 2A-2D),activating an escape function on dynamic function row 104 may pause thegame.

In some embodiments, functions may be associated with combinations ofmovably actuated keys and/or user-selectable symbols. For example,simultaneous actuation of a command key and “c” key (i.e., command+c)may be associated with a “copy” function. In another example,simultaneous actuation of the command key and selection of theuser-selectable symbol with the indicator “esc” (i.e., command+esc) mayactivate a function to open a particular application such as a mediaplayer application. In yet another example, simultaneous selection oftwo user-selectable symbols (e.g., the user-selectable symbol with theindicator “esc” and the user-selectable symbol 144 with the magnifyingglass indicator) may result in activation of a function, such as aspecialized search function.

In some embodiments, a first subset 146 of the one or moreuser-selectable symbols 142 of dynamic function row 104 may beassociated with one group of functions and a second subset 148 of theone or more user-selectable symbols 142 of dynamic function row 104 maybe associated with a second group of functions. For example, theuser-selectable symbols in first subset 146 may be global functions(e.g., system-level functions or affordances), and the user-selectablesymbols in second subset 148 may be application-specific functions. Assuch, the user-selectable symbols in second subset 148 change when thefocus shifts from a first element of a graphical user interfacedisplayed on primary display 102 (e.g., a first window corresponding toan Internet browser application) to a second element of the graphicaluser interface (e.g., a second window corresponding to an e-mailapplication). In contrast, the user-selectable symbols in first subset146 are maintained when the focus shifts from the first element of thegraphical user interface to the second element of the graphical userinterface.

In some embodiments, the user-selectable symbols in second subset 148are determined based on an active user interface element display onprimary display 102 that is in focus. In some embodiments, the term “infocus” can refer to the active element of the user interface (e.g., awindow associated with an application, a particular toolbar or menuassociated with an application, or the operating system) that iscurrently in the foreground and actively running or is controllable byinput received from a user of the computing system such as a key press,mouse click, voice command, gestural motion, or the like.

In some embodiments, the first subset 146 of the one or moreuser-selectable symbols 142 corresponding to global user-selectablesymbols occupies a first area of dynamic function row 104 (e.g., theleft half of dynamic function row 104), and the second subset 148 of theone or more user-selectable symbols 142 occupies a second area ofdynamic function row 104 (e.g., the right half of dynamic function row104). It will be realized that other proportions of dynamic function row104 may be allocated to the first subset 146 and the second subset 148.In some embodiments, when no application has focus, the second area ofdynamic function row 104 may not include any user-selectable symbols. Insome embodiments, dynamic function row 104 includes three or moresubsets of user-selectable symbols. In some embodiments, dynamicfunction row 104 includes a single set of user-selectable symbols thatare not divided into subsets. While a single row of user-selectablesymbols are shown in dynamic function row 104 in FIG. 1B, it will berecognized that dynamic function row 104 may include multiple rows ofuser-selectable symbols.

In some embodiments, the change in focus changes which element of thegraphical user interface displayed on primary display 102 of displayportion 110 (or peripheral display device 204, FIGS. 2A-2D) is activeand which element will receive user input. The user input may bereceived from a keyboard, mouse, touchpad, or other user input device.Additionally and/or alternatively, in some embodiments, the change infocus changes an element that is shown in the foreground of a graphicaluser interface displayed on primary display 102 of display portion 110(or peripheral display device 204, FIGS. 2A-2D).

In some embodiments, the change in focus occurs in response to userinput, for example, in response to user selection of an element of agraphical user interface (e.g., a different window) displayed on primarydisplay 102 of display portion 110 (or peripheral display device 204,FIGS. 2A-2D) or in response to user selection of a user-selectablesymbol (e.g., one of the affordances/symbols displayed on dynamicfunction row 104). The user selection may be a key stroke, a mouseclick, a mouse over, a command+tab input, or the like. In someembodiments, the change in focus occurs in response to a determinationby an operating system of portable system 100 (or computing device 202in FIGS. 2A-2D). For example, when a user closes an application windowthat has focus, the operating system may give focus to a differentapplication, such as an application that had focus prior to the closedapplication window. In another example, when a user closes anapplication window that has focus, the operating system may give focusto a dialog box prompting the user to save changes made to a documentvia the application.

In some embodiments, the change in focus may be a change from oneelement associated with an application to another element associatedwith the same application (e.g., from an e-mail composition window of ane-mail application to an inbox list window of an e-mail application orfrom one tab of an Internet browser application to another tab of anInternet browser application). In some embodiments, the change in focusmay be a change from an element associated with one application to anelement associated with another application (e.g., from an Internetbrowser window to an e-mail application window). Further, in someembodiments, the change in focus may be a change from an elementassociated with an application to an element associated with anoperating system, such as a system dialog box, a system setting control(e.g., volume control), a window associated with a file/foldernavigation application (e.g., Apple Inc.'s FINDER application), etc.Additionally, focus may also be directed to a dialog box, filedirectory, setting control (e.g., volume control), or any other elementof a graphical user interface for which information can be presented toa user and/or user input can be received.

FIG. 2A is an illustrative diagram of a first implementation of desktopcomputing system 200 in accordance with some embodiments. Desktopcomputing system 200 includes a computing device 202, a peripheraldisplay device 204 with primary display 102, a peripheral keyboard 206,and a peripheral mouse 208. Computing device 202 includes one or moreprocessors and memory storing one or more programs for execution by theone or more processors. In some embodiments, peripheral display device204 may be integrated with computing device 202 such as an iMAC® device.In some embodiments, primary display 102 of peripheral display device204 is a touch screen display. In FIG. 2A, peripheral display device 204(also referred to herein as a first housing 204 or housing 204),peripheral keyboard 206, and peripheral mouse 208 are communicativelycoupled to computing device 202 via a wired connection, such as USB orPS/2, or via a wireless communication link, using a communicationprotocol such as Bluetooth, Wi-Fi, or the like. For example, peripheralkeyboard 206 (also referred to herein as second housing 206 or housing206) is not more than fifteen feet from computing device 202 (e.g.approximately three feet away). In FIG. 2A, peripheral keyboard 206includes dynamic function row 104 and a set of physical keys 106 atleast partially contained within a same housing. In some embodiments,dynamic function row 104, which is described in more detail withreference to FIG. 1B, is a touch screen display. In some embodiments,peripheral keyboard 206 includes one or more processors and memorystoring one or more programs that may be executed by the one or moreprocessors of peripheral keyboard 206 to perform any of the embodimentsdescribed herein. In some embodiments, peripheral keyboard 206 relayssignals indicating user inputs (e.g., key strokes and selections ofuser-selectable symbols/affordances displayed by dynamic function row104) to computing device 202.

FIG. 2B is an illustrative diagram of a second implementation of desktopcomputing system 200 in accordance with some embodiments. In FIG. 2B,desktop computing system 200 includes a computing device 202, aperipheral display device 204 with primary display 102, and a peripheralkeyboard 206. In FIG. 2B, peripheral display device 204 and peripheralkeyboard 206 are communicatively coupled to computing device 202 via awired connection, such as USB or PS/2, or via a wireless communicationlink, using a communication protocol such as Bluetooth, Wi-Fi, or thelike. In FIG. 2B, peripheral keyboard 206 includes dynamic function row104, a set of physical keys 106, and touchpad 108 at least partiallycontained within a same housing. In some embodiments, dynamic functionrow 104, which is described in more detail with reference to FIG. 1B, isa touch screen display. In some embodiments, peripheral keyboard 206includes one or more processors and memory storing one or more programsthat may be executed by the one or more processors of peripheralkeyboard 206 to perform any of the embodiments described herein. In someembodiments, peripheral keyboard 206 relays signals indicating userinputs (e.g., key strokes, user interactions with touchpad 108, andselections of user-selectable symbols/affordances displayed by dynamicfunction row 104) to computing device 202.

FIG. 2C is an illustrative diagram of a third implementation of desktopcomputing system 200 in accordance with some embodiments. In FIG. 2C,desktop computing system 200 includes a computing device 202, aperipheral display device 204 with primary display 102, a peripheralkeyboard 206, and a first peripheral input mechanism 212. In FIG. 2C,peripheral display device 204, peripheral keyboard 206, and the firstperipheral input mechanism 212 are communicatively coupled to computingdevice 202 via a wired connection, such as USB or PS/2, or via awireless communication link, using a communication protocol such asBluetooth, Wi-Fi, or the like. In FIG. 2C, peripheral keyboard 206includes a set of physical keys 106, and the first peripheral inputmechanism 212 includes dynamic function row 104 and touchpad 108 atleast partially contained within a same housing. In some embodiments,dynamic function row 104, which is described in more detail withreference to FIG. 1B, is a touch screen display. In some embodiments,the first peripheral input mechanism 212 includes one or more processorsand memory storing one or more programs that may be executed by the oneor more processors of the first peripheral input mechanism 212 toperform any of the embodiments described herein. In some embodiments,the first peripheral input mechanism 212 relays signals indicating userinputs (e.g., user interactions with touchpad 108 and user selections ofuser-selectable symbols/affordances displayed by dynamic function row104) to computing device 202.

FIG. 2D is an illustrative diagram of a fourth implementation of desktopcomputing system 200 in accordance with some embodiments. In FIG. 2D,desktop computing system 200 includes a computing device 202, aperipheral display device 204 with primary display 102, a peripheralkeyboard 206, a peripheral mouse 208, and a second peripheral inputmechanism 222. In FIG. 2D, peripheral display device 204, peripheralkeyboard 206, peripheral mouse 208, and the second peripheral inputmechanism 222 are communicatively coupled to computing device 202 via awired connection, such as USB or PS/2, or via a wireless communicationlink, using a communication protocol such as Bluetooth, Wi-Fi, or thelike. In FIG. 2A, peripheral keyboard 206 includes dynamic function row104 and a set of physical keys 106. In FIG. 2D, peripheral keyboard 206includes a set of physical keys 106, and the second peripheral inputmechanism 222 includes dynamic function row 104 at least partiallycontained within the housing of the second peripheral input mechanism222. In some embodiments, dynamic function row 104, which is describedin more detail with reference to FIG. 1B, is a touch screen display. Insome embodiments, the second peripheral input mechanism 222 includes oneor more processors and memory storing one or more programs that may beexecuted by the one or more processors of the second peripheral inputmechanism 222 to perform any of the embodiments described herein. Insome embodiments, the second peripheral input mechanism 222 relayssignals indicating user inputs (e.g., user selections of user-selectablesymbols/affordances displayed by dynamic function row 104) to computingdevice 202.

FIG. 3A is a block diagram of an electronic device 300, in accordancewith some embodiments. In some embodiments, electronic device 300 is aportable electronic device, such as a laptop (e.g., portable computingsystem 100, FIG. 1A). In some embodiments, electronic device 300 is nota portable device, but is a desktop computer (e.g., computing device 202of desktop computing system 200, FIGS. 2A-2D), which is communicativelycoupled with a peripheral display system (e.g., peripheral displaydevice 204, FIGS. 2A-2D) and optionally a peripheral touch-sensitivesurface (e.g., a touchpad 108, FIGS. 2B-2C and/or a touch-sensitivedisplay, such as peripheral display device 204, FIGS. 2A-2D and/ordynamic function row 104, FIGS. 2A-2D).

Electronic device 300 typically supports a variety of applications, suchas one or more of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a video conferencing application, an e-mailapplication, an instant messaging application, an image managementapplication, a digital camera application, a digital video cameraapplication, a web browser application, and/or a media playerapplication.

The various applications that are executed on electronic device 300optionally use at least one common physical user-interface device, suchas the touch-sensitive surface. One or more functions of thetouch-sensitive surface as well as corresponding information displayedby electronic device 300 are, optionally, adjusted and/or varied fromone application to the next and/or within an application. In this way, acommon physical architecture (such as the touch-sensitive surface) ofelectronic device 300 optionally supports the variety of applicationswith user interfaces that are intuitive and transparent to the user.

Electronic device 300 includes memory 302 (which optionally includes oneor more computer readable storage mediums), memory controller 322, oneor more processing units (CPU(s)) 320, peripherals interface 318, RFcircuitry 308, audio circuitry 310, speaker 311, microphone 313,input/output (I/O) subsystem 306, other input or control devices 316,and external port 324. Electronic device 300 optionally includes adisplay system 312 (e.g., primary display 102 of display portion 110,FIG. 1A and/or dynamic function row 104, FIGS. 1A-1B), which may be atouch-sensitive display (sometimes also herein called a “touch screen”or a “touch screen display”). Electronic device 300 optionally includesone or more optical sensors 364. Electronic device 300 optionallyincludes one or more intensity sensors 365 for detecting intensity ofcontacts on a touch-sensitive surface such as touch-sensitive display ora touchpad. Electronic device 300 optionally includes one or moretactile output generators 367 for generating tactile outputs on atouch-sensitive surface such as touch-sensitive display or a touchpad(e.g., touchpad 108, FIGS. 1A-1B). These components optionallycommunicate over one or more communication buses or signal lines 303.

As used in the specification, the term “intensity” of a contact on atouch-sensitive surface refers to the force or pressure (force per unitarea) of a contact (e.g., a finger contact) on the touch sensitivesurface, or to a substitute (proxy) for the force or pressure of acontact on the touch sensitive surface. The intensity of a contact has arange of values that includes at least four distinct values and moretypically includes hundreds of distinct values (e.g., at least 256).Intensity of a contact is, optionally, determined (or measured) usingvarious approaches and various sensors or combinations of sensors. Forexample, one or more force sensors underneath or adjacent to thetouch-sensitive surface are, optionally, used to measure force atvarious points on the touch-sensitive surface. In some implementations,force measurements from multiple force sensors are combined (e.g., aweighted average) to determine an estimated force of a contact.Similarly, a pressure-sensitive tip of a stylus is, optionally, used todetermine a pressure of the stylus on the touch-sensitive surface.Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure and the estimated force or pressure isused to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or touch/track pad) is,optionally, interpreted by the user as a “down click” or “up click” of aphysical actuator button. In some cases, a user will feel a tactilesensation such as an “down click” or “up click” even when there is nomovement of a physical actuator button associated with thetouch-sensitive surface that is physically pressed (e.g., displaced) bythe user's movements. As another example, movement of thetouch-sensitive surface is, optionally, interpreted or sensed by theuser as “roughness” of the touch-sensitive surface, even when there isno change in smoothness of the touch-sensitive surface. While suchinterpretations of touch by a user will be subject to the individualizedsensory perceptions of the user, there are many sensory perceptions oftouch that are common to a large majority of users. Thus, when a tactileoutput is described as corresponding to a particular sensory perceptionof a user (e.g., an “up click,” a “down click,” “roughness”), unlessotherwise stated, the generated tactile output corresponds to physicaldisplacement of the device or a component thereof that will generate thedescribed sensory perception for a typical (or average) user.

It should be appreciated that electronic device 300 is only an exampleand that electronic device 300 optionally has more or fewer componentsthan shown, optionally combines two or more components, or optionallyhas a different configuration or arrangement of the components. Thevarious components shown in FIG. 3A are implemented in hardware,software, firmware, or a combination thereof, including one or moresignal processing and/or application specific integrated circuits.

Memory 302 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 302 by othercomponents of electronic device 300, such as CPU(s) 320 and peripheralsinterface 318, is, optionally, controlled by memory controller 322.Peripherals interface 318 can be used to couple input and outputperipherals to CPU(s) 320 and memory 302. The one or more processingunits 320 run or execute various software programs and/or sets ofinstructions stored in memory 302 to perform various functions forelectronic device 300 and to process data. In some embodiments,peripherals interface 318, CPU(s) 320, and memory controller 322 are,optionally, implemented on a single chip, such as chip 304. In someother embodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 308 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 308 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 308 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 308 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The wirelesscommunication optionally uses any of a plurality of communicationsstandards, protocols and technologies, including but not limited toGlobal System for Mobile Communications (GSM), Enhanced Data GSMEnvironment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a,IEEE 802.11b, IEEE 802.11g, and/or IEEE 802.11n), voice over InternetProtocol (VoIP), Wi-MAX, a protocol for e-mail (e.g., Internet messageaccess protocol (IMAP) and/or post office protocol (POP)), instantmessaging (e.g., extensible messaging and presence protocol (XMPP),Session Initiation Protocol for Instant Messaging and PresenceLeveraging Extensions (SIMPLE), Instant Messaging and Presence Service(IMPS)), and/or Short Message Service (SMS), or any other suitablecommunication protocol, including communication protocols not yetdeveloped as of the filing date of this document.

Audio circuitry 310, speaker 311, and microphone 313 provide an audiointerface between a user and electronic device 300. Audio circuitry 310receives audio data from peripherals interface 318, converts the audiodata to an electrical signal, and transmits the electrical signal tospeaker 311. Speaker 311 converts the electrical signal to human-audiblesound waves. Audio circuitry 310 also receives electrical signalsconverted by microphone 313 from sound waves. Audio circuitry 310converts the electrical signals to audio data and transmits the audiodata to peripherals interface 318 for processing. Audio data is,optionally, retrieved from and/or transmitted to memory 302 and/or RFcircuitry 308 by peripherals interface 318. In some embodiments, audiocircuitry 310 also includes a headset jack. The headset jack provides aninterface between audio circuitry 310 and removable audio input/outputperipherals, such as output-only headphones or a headset with bothoutput (e.g., a headphone for one or both ears) and input (e.g., amicrophone).

I/O subsystem 306 couples the input/output peripherals of electronicdevice 300, such as display system 312 and other input or controldevices 316, to peripherals interface 318. I/O subsystem 306 optionallyincludes display controller 356, optical sensor controller 358,intensity sensor controller 359, haptic feedback controller 361, and oneor more other input controllers 360 for other input or control devices.The one or more other input controllers 360 receive/send electricalsignals from/to other input or control devices 316. The other input orcontrol devices 316 optionally include physical buttons (e.g., pushbuttons, rocker buttons, etc.), dials, slider switches, joysticks, clickwheels, and so forth. In some alternate embodiments, other inputcontroller(s) 360 are, optionally, coupled with any (or none) of thefollowing: a keyboard, infrared port, USB port, and a pointer devicesuch as a mouse. The one or more physical buttons optionally include anup/down button for volume control of speaker 311 and/or microphone 313.

Display system 312 (e.g., primary display 102 of display portion 110,FIG. 1A and/or dynamic function row 104, FIGS. 1A-1B) provides an outputinterface (and, optionally, an input interface when it is atouch-sensitive display) between electronic device 300 and a user.Display controller 356 receives and/or sends electrical signals from/todisplay system 312. Display system 312 displays visual output to theuser. The visual output optionally includes graphics, text, icons,video, and any combination thereof (collectively termed “graphics”). Insome embodiments, some or all of the visual output corresponds touser-interface objects/elements.

In some embodiments, display system 312 (e.g., primary display 102 ofdisplay portion 110, FIG. 1A and/or dynamic function row 104, FIGS.1A-1B) is a touch-sensitive display with a touch-sensitive surface,sensor, or set of sensors that accepts input from the user based onhaptic and/or tactile contact. As such, display system 312 and displaycontroller 356 (along with any associated modules and/or sets ofinstructions in memory 302) detect contact (and any movement or breakingof the contact) on display system 312 and convert the detected contactinto interaction with user-interface objects (e.g., one or more softkeys, icons, web pages, or images) that are displayed on display system312. In one example embodiment, a point of contact between displaysystem 312 and the user corresponds to an area under a finger of theuser.

Display system 312 (e.g., primary display 102 of display portion 110,FIG. 1A and/or dynamic function row 104, FIGS. 1A-1B) optionally usesLCD (liquid crystal display) technology, LPD (light emitting polymerdisplay) technology, LED (light emitting diode) technology, or OLED(organic light emitting diode) technology, although other displaytechnologies are used in other embodiments. In some embodiments, whendisplay system 312 is a touch-sensitive display, display system 312 anddisplay controller 356 optionally detect contact and any movement orbreaking thereof using any of a plurality of touch sensing technologiesnow known or later developed, including but not limited to capacitive,resistive, infrared, and surface acoustic wave technologies, as well asother proximity sensor arrays or other elements for determining one ormore points of contact with display system 312. In one exampleembodiment, projected mutual capacitance sensing technology is used,such as that found in the iPHONE®, iPODTOUCH®, and iPAD® from Apple Inc.of Cupertino, Calif.

Display system 312 (e.g., primary display 102 of display portion 110,FIG. 1A and/or dynamic function row 104, FIGS. 1A-1B) optionally has avideo resolution in excess of 400 dpi (e.g., 500 dpi, 800 dpi, orgreater). In some embodiments, display system 312 is a touch-sensitivedisplay with which the user optionally makes contact using a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures. Insome embodiments, electronic device 300 translates the roughfinger-based input into a precise pointer/cursor position or command forperforming the actions desired by the user.

In some embodiments, in addition to display system 312, electronicdevice 300 optionally includes a touchpad (e.g., touchpad 108, FIGS.1A-1B) for activating or deactivating particular functions. In someembodiments, the touchpad is a touch-sensitive area of electronic device300 that, unlike display system 312, does not display visual output. Insome embodiments, when display system 312 is a touch-sensitive display,the touchpad is, optionally, a touch-sensitive surface that is separatefrom display system 312, or an extension of the touch-sensitive surfaceformed by display system 312.

Electronic device 300 also includes power system 362 for powering thevarious components. Power system 362 optionally includes a powermanagement system, one or more power sources (e.g., battery, alternatingcurrent (AC), etc.), a recharging system, a power failure detectioncircuit, a power converter or inverter, a power status indicator (e.g.,a light-emitting diode (LED)) and any other components associated withthe generation, management and distribution of power in portabledevices.

Electronic device 300 optionally also includes one or more opticalsensors 364 coupled with optical sensor controller 358 in I/O subsystem306. Optical sensor(s) 364 optionally includes charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor(s) 364 receive light from theenvironment, projected through one or more lens, and converts the lightto data representing an image. In conjunction with imaging module 343,optical sensor(s) 364 optionally capture still images or video. In someembodiments, an optical sensor is located on the front of electronicdevice 300 so that the user's image is, optionally, obtained forvideoconferencing while the user views the other video conferenceparticipants on display system 312.

Electronic device 300 optionally also includes one or more contactintensity sensor(s) 365 coupled with intensity sensor controller 359 inI/O subsystem 306. Contact intensity sensor(s) 365 optionally includesone or more piezoresistive strain gauges, capacitive force sensors,electric force sensors, piezoelectric force sensors, optical forcesensors, capacitive touch-sensitive surfaces, or other intensity sensors(e.g., sensors used to measure the force (or pressure) of a contact on atouch-sensitive surface). Contact intensity sensor(s) 365 receivescontact intensity information (e.g., pressure information or a proxy forpressure information) from the environment. In some embodiments, atleast one contact intensity sensor is collocated with, or proximate to,a touch-sensitive surface (e.g., touchpad 108, FIGS. 1A-1B or displaysystem 312 when it is a touch-sensitive display).

Electronic device 300 optionally also includes one or more tactileoutput generators 367 coupled with haptic feedback controller 361 in I/Osubsystem 306. Tactile output generator(s) 367 optionally includes oneor more electroacoustic devices such as speakers or other audiocomponents and/or electromechanical devices that convert energy intolinear motion such as a motor, solenoid, electroactive polymer,piezoelectric actuator, electrostatic actuator, or other tactile outputgenerating component (e.g., a component that converts electrical signalsinto tactile outputs on the device). Contact intensity sensor(s) 365receives tactile feedback generation instructions from haptic feedbackmodule 333 and generates tactile outputs that are capable of beingsensed by a user of electronic device 300. In some embodiments, at leastone tactile output generator is collocated with, or proximate to, atouch-sensitive surface (e.g., touchpad 108, FIGS. 1A-1B or displaysystem 312 when it is a touch-sensitive display) and, optionally,generates a tactile output by moving the touch-sensitive surfacevertically (e.g., in/out of a surface of electronic device 300) orlaterally (e.g., back and forth in the same plane as a surface ofelectronic device 300).

Electronic device 300 optionally also includes one or more proximitysensors 366 coupled with peripherals interface 318. Alternately,proximity sensor(s) 366 are coupled with other input controller(s) 360in I/O subsystem 306. Electronic device 300 optionally also includes oneor more accelerometers 368 coupled with peripherals interface 318.Alternately, accelerometer(s) 368 are coupled with other inputcontroller(s) 360 in I/O subsystem 306.

In some embodiments, the software components stored in memory 302include operating system 326, communication module 328 (or set ofinstructions), contact/motion module 330 (or set of instructions),graphics module 332 (or set of instructions), applications 340 (or setsof instructions), and touch-bar management module 350 (or sets ofinstructions). Furthermore, in some embodiments, memory 302 storesdevice/global internal state 357 (or sets of instructions), as shown inFIG. 3A. Device/global internal state 357 includes one or more of:active application state, indicating which applications, if any, arecurrently active and/or in focus; display state, indicating whatapplications, views or other information occupy various regions ofdisplay system 312 (e.g., primary display 102 of display portion 110,FIG. 1A and/or dynamic function row 104, FIGS. 1A-1B) and/or aperipheral display system (e.g., primary display 102 of peripheraldisplay device 204, FIGS. 2A-2D and/or dynamic function row 104, FIGS.2A-2D); sensor state, including information obtained from varioussensors and input or control devices 316 of electronic device 300; andlocation information concerning the location and/or attitude ofelectronic device 300.

Operating system 326 (e.g., DARWIN, RTXC, LINUX, UNIX, OS X, WINDOWS, oran embedded operating system such as VXWorks) includes various softwarecomponents and/or drivers for controlling and managing general systemtasks (e.g., memory management, storage device control, powermanagement, etc.) and facilitates communication between various hardwareand software components.

Communication module 328 facilitates communication with other devices(e.g., computing device 202, FIGS. 2A-2D; peripheral mouse 208, FIGS. 2Aand 2D; peripheral keyboard 206, FIGS. 2A-2B; first peripheral inputmechanism 212, FIG. 2C; and/or second peripheral input mechanism 222,FIG. 2D) over one or more external ports 324 and/or RF circuitry 308 andalso includes various software components for sending/receiving data viaRF circuitry 308 and/or external port 324. External port 324 (e.g.,Universal Serial Bus (USB), FIREWIRE, etc.) is adapted for couplingdirectly to other devices or indirectly over a network (e.g., theInternet, wireless LAN, etc.). In some embodiments, external port 324 isa multi-pin (e.g., 30-pin) connector that is the same as, or similar toand/or compatible with the 30-pin connector used on iPod® devices.

Contact/motion module 330 optionally detects contact with display system312 when it is a touch-sensitive display (in conjunction with displaycontroller 356) and other touch sensitive devices (e.g., a touchpad orphysical click wheel). Contact/motion module 330 includes varioussoftware components for performing various operations related todetection of contact, such as determining if contact has occurred (e.g.,detecting a finger-down event), determining an intensity of the contact(e.g., the force or pressure of the contact or a substitute for theforce or pressure of the contact), determining if there is movement ofthe contact and tracking the movement across the touch-sensitive surface(e.g., detecting one or more finger-dragging events), and determining ifthe contact has ceased (e.g., detecting a finger-up event or a break incontact). Contact/motion module 330 receives contact data from thetouch-sensitive surface. Determining movement of the point of contact,which is represented by a series of contact data, optionally includesdetermining speed (magnitude), velocity (magnitude and direction),and/or an acceleration (a change in magnitude and/or direction) of thepoint of contact. These operations are, optionally, applied to singlecontacts (e.g., one finger contacts) or to multiple simultaneouscontacts (e.g., “multitouch”/multiple finger contacts). In someembodiments, contact/motion module 330 also detects contact on atouchpad (e.g., touchpad 108, FIGS. 1A-1B).

In some embodiments, contact/motion module 330 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has selected or“clicked” on an affordance). In some embodiments at least a subset ofthe intensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of electronic device300). For example, a mouse “click” threshold of a trackpad or touchscreen display can be set to any of a large range of predefinedthresholds values without changing the trackpad or touch screen displayhardware. Additionally, in some implementations a user of the device isprovided with software settings for adjusting one or more of the set ofintensity thresholds (e.g., by adjusting individual intensity thresholdsand/or by adjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

Contact/motion module 330 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap contact includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and in some embodimentsalso followed by detecting a finger-up (lift off) event.

Graphics module 332 includes various known software components forrendering and causing display of graphics on primary display 102 (e.g.,primary display 102 of display portion 110, FIG. 1A or primary display102 of peripheral display device 204, FIGS. 2A-2D) or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast or other visual property) of graphicsthat are displayed. As used herein, the term “graphics” includes anyobject that can be displayed to a user, including without limitationtext, web pages, icons (such as user-interface objects including softkeys), digital images, videos, animations and the like. In someembodiments, graphics module 332 stores data representing graphics to beused. Each graphic is, optionally, assigned a corresponding code.Graphics module 332 receives, from applications etc., one or more codesspecifying graphics to be displayed along with, if necessary, coordinatedata and other graphic property data, and then generates screen imagedata to output to display controller 356.

Haptic feedback module 333 includes various software components forgenerating instructions used by tactile output generator(s) 367 toproduce tactile outputs at one or more locations on electronic device300 in response to user interactions with electronic device 300.

Applications 340 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   e-mail client module 341 (sometimes also herein called “mail        app” or “e-mail app”) for receiving, sending, composing, and        viewing e-mails;    -   imaging module 342 for capturing still and/or video images;    -   image management module 343 (sometimes also herein called “photo        app”) for editing and viewing still and/or video images;    -   media player module 344 (sometimes also herein called “media        player app”) for playback of audio and/or video; and    -   web browsing module 345 (sometimes also herein called “web        browser”) for connecting to and browsing the Internet.

Examples of other applications 340 that are, optionally, stored inmemory 302 include messaging and communications applications, wordprocessing applications, other image editing applications, drawingapplications, presentation applications, JAVA-enabled applications,encryption applications, digital rights management applications, voicerecognition applications, and voice replication applications.

In conjunction with one or more of RF circuitry 308, display system 312(e.g., primary display 102 of display portion 110, FIG. 1A and/ordynamic function row 104, FIGS. 1A-1B), display controller 356, andcontact module 330, graphics module 332, e-mail client module 341includes executable instructions to create, send, receive, and managee-mail in response to user instructions. In conjunction with imagemanagement module 343, e-mail client module 341 makes it very easy tocreate and send e-mails with still or video images taken with imagingmodule 342.

In conjunction with one or more of display system 312 (e.g., primarydisplay 102 of display portion 110, FIG. 1A and/or dynamic function row104, FIGS. 1A-1B), display controller 356, optical sensor(s) 364,optical sensor controller 358, contact module 330, graphics module 332,and image management module 343, imaging module 342 includes executableinstructions to capture still images or video (including a video stream)and store them into memory 302, modify characteristics of a still imageor video, or delete a still image or video from memory 302.

In conjunction with one or more of display system 312 (e.g., primarydisplay 102 of display portion 110, FIG. 1A and/or dynamic function row104, FIGS. 1A-1B), display controller 356, contact module 330, graphicsmodule 332, and imaging module 342, image management module 343 includesexecutable instructions to arrange, modify (e.g., edit), or otherwisemanipulate, label, delete, present (e.g., in a digital slide show oralbum), and store still and/or video images.

In conjunction with one or more of display system 312 (e.g., primarydisplay 102 of display portion 110, FIG. 1A and/or dynamic function row104, FIGS. 1A-1B), display controller 356, contact module 330, graphicsmodule 332, audio circuitry 310, speaker 311, RF circuitry 308, and webbrowsing module 345, media player module 344 includes executableinstructions that allow the user to download and play back recordedmusic and other sound files stored in one or more file formats, such asMP3 or AAC files, and executable instructions to display, present orotherwise play back videos (e.g., on primary display 102 of displayportion 110, FIG. 1A or primary display 102 of peripheral display device2014, FIGS. 2A-2B connected via external port 324).

In conjunction with one or more of RF circuitry 308, display system 312(e.g., primary display 102 of display portion 110, FIG. 1A and/ordynamic function row 104, FIGS. 1A-1B), display controller 356, contactmodule 330, and graphics module 332, web browsing module 345 includesexecutable instructions to browse the Internet in accordance with userinstructions, including searching, linking to, receiving, and displayingweb pages or portions thereof, as well as attachments and other fileslinked to web pages.

Touch-bar management module 350 includes: focus determining module 351,presenting module 352, and mode associating module 353. The touch-barmanagement module 350 manages operations of the touch-sensitivesecondary display 104 and, in particular, determines when to operate thetouch-sensitive secondary display in various display modes. An examplealgorithm used by the touch-bar management module 350, in someembodiments, to determine which display mode in which to operate thetouch-sensitive secondary display 104 is shown in FIG. 8.

With reference now to FIG. 8, in some embodiments, focus determiningmodule 351 is configured to detect (802) (and/or receive informationabout) a change in focus to a respective user interface within agraphical user interface displayed by display system 312 (e.g., primarydisplay 102 of display portion 110, FIG. 1A) or a peripheral displaysystem (e.g., peripheral display device 204, FIGS. 2A-2D).

In some embodiments, after the focus determining module 351 has detectedthat the respective user interface is in focus, the mode associatingmodule 353 can then determine (804) whether an application associatedwith the user interface has been associated with a particular displaymode for the touch-sensitive secondary display (e.g., using a touch-barmanagement user interface, as is discussed in detail below in referenceto method 700). In accordance with a determination that the applicationhas been associated with the respective display mode for thetouch-sensitive secondary display (804—Yes), then the presenting module352 is configured to cause the secondary display to operate in theparticular display mode (806). In accordance with a determination thatthe application has not been associated with a respective display modefor the touch-sensitive secondary display (804—No), then the presentingmodule 352 is configured to cause the secondary display to operate in acurrent system-wide display mode for the touch-sensitive secondarydisplay (808) (e.g., a persistent display mode selected by a user aftera mode-switching input is provided, as is explained below in referenceto method 600 and/or a current default display mode that is defined bythe system, such as an adaptive display mode).

In some embodiments, the method 800 then returns back to operation 802each time that a change in focus is detected at the primary display, sothat the touch-bar management module 350 can again determine anappropriate display mode in which to operate the touch-sensitivesecondary display after each change in focus is detected. The method 800can be used in conjunction with method 600 described in more detailbelow, such that as various focus changes are detected at the primarydisplay algorithm 800 is utilized to ensure that the secondary displayis operated in the proper display mode after these various focuschanges.

Each of the above identified modules and applications correspond to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 302 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 302 optionally stores additionalmodules and data structures not described above.

FIG. 3B is a block diagram of components for event handling of FIG. 3A,in accordance with some embodiments. In some embodiments, memory 302(FIG. 3A) includes event sorter 370 (e.g., in operating system 326) andan application 340-1 (e.g., any of the aforementioned applications 341,342, 343, 344, or 345).

Event sorter 370 receives event information and determines theapplication 340-1 and application view 391 of application 340-1 to whichto deliver the event information. Event sorter 370 includes eventmonitor 371 and event dispatcher module 374. In some embodiments,application 340-1 includes application internal state 392, whichindicates the current application view(s) displayed on display system312 (e.g., primary display 102 of display portion 110, FIG. 1A and/ordynamic function row 104, FIGS. 1A-1B) when the application is active orexecuting. In some embodiments, device/global internal state 357 is usedby event sorter 370 to determine which application(s) is (are) currentlyactive or in focus, and application internal state 392 is used by eventsorter 370 to determine application views 391 to which to deliver eventinformation.

In some embodiments, application internal state 392 includes additionalinformation, such as one or more of: resume information to be used whenapplication 340-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 340-1, a state queue for enabling the user to go back toa prior state or view of application 340-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 371 receives event information from peripherals interface318. Event information includes information about a sub-event (e.g., auser touch on display system 312 when it is a touch-sensitive display,as part of a multi-touch gesture). Peripherals interface 318 transmitsinformation it receives from I/O subsystem 306 or a sensor, such asproximity sensor(s) 366, accelerometer(s) 368, and/or microphone 313(through audio circuitry 310). Information that peripherals interface318 receives from I/O subsystem 306 includes information from displaysystem 312 when it is a touch-sensitive display or anothertouch-sensitive surface (e.g., touchpad 108, FIGS. 1A-1B).

In some embodiments, event monitor 371 sends requests to the peripheralsinterface 318 at predetermined intervals. In response, peripheralsinterface 318 transmits event information. In other embodiments,peripheral interface 318 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 370 also includes a hit viewdetermination module 372 and/or an active event recognizer determinationmodule 373.

Hit view determination module 372 provides software procedures fordetermining where a sub-event has taken place within one or more views,when display system 312 displays more than one view, where views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of an application) in which atouch is detected optionally correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected is, optionally, calledthe hit view, and the set of events that are recognized as proper inputsare, optionally, determined based, at least in part, on the hit view ofthe initial touch that begins a touch-based gesture.

Hit view determination module 372 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 372identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (i.e., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule, the hit view typically receives all sub-events related to thesame touch or input source for which it was identified as the hit view.

Active event recognizer determination module 373 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 373 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 373 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 374 dispatches the event information to an eventrecognizer (e.g., event recognizer 380). In embodiments including activeevent recognizer determination module 373, event dispatcher module 374delivers the event information to an event recognizer determined byactive event recognizer determination module 373. In some embodiments,event dispatcher module 374 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 382.

In some embodiments, operating system 326 includes event sorter 370.Alternatively, application 340-1 includes event sorter 370. In yet otherembodiments, event sorter 370 is a stand-alone module, or a part ofanother module stored in memory 302, such as contact/motion module 330.

In some embodiments, application 340-1 includes a plurality of eventhandlers 390 and one or more application views 391, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 391 of the application 340-1 includes one or more event recognizers380. Typically, an application view 391 includes a plurality of eventrecognizers 380. In other embodiments, one or more of event recognizers380 are part of a separate module, such as a user interface kit (notshown) or a higher level object from which application 340-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 390 includes one or more of: data updater 376, object updater377, GUI updater 378, and/or event data 379 received from event sorter370. Event handler 390 optionally utilizes or calls data updater 376,object updater 377 or GUI updater 378 to update the application internalstate 392. Alternatively, one or more of the application views 391includes one or more respective event handlers 390. Also, in someembodiments, one or more of data updater 376, object updater 377, andGUI updater 378 are included in an application view 391.

A respective event recognizer 380 receives event information (e.g.,event data 379) from event sorter 370, and identifies an event from theevent information. Event recognizer 380 includes event receiver 382 andevent comparator 384. In some embodiments, event recognizer 380 alsoincludes at least a subset of: metadata 383, and event deliveryinstructions 388 (which optionally include sub-event deliveryinstructions).

Event receiver 382 receives event information from event sorter 370. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 384 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 384 includes eventdefinitions 386. Event definitions 386 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(387-1), event 2 (387-2), and others. In some embodiments, sub-events inan event 387 include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (387-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first lift-off (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second lift-off (touchend) for a predetermined phase. In another example, the definition forevent 2 (387-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across display system 312when it is a touch-sensitive display, and lift-off of the touch (touchend). In some embodiments, the event also includes information for oneor more associated event handlers 390.

In some embodiments, event definition 387 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 384 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed on displaysystem 312, when a touch is detected on display system 312 when it is atouch-sensitive display, event comparator 384 performs a hit test todetermine which of the three user-interface objects is associated withthe touch (sub-event). If each displayed object is associated with arespective event handler 390, the event comparator uses the result ofthe hit test to determine which event handler 390 should be activated.For example, event comparator 384 selects an event handler associatedwith the sub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event 387 alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 380 determines that the series ofsub-events do not match any of the events in event definitions 386, therespective event recognizer 380 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 380 includes metadata383 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 383 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 383 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 380 activates eventhandler 390 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 380 delivers event information associated with theevent to event handler 390. Activating an event handler 390 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 380 throws a flag associated withthe recognized event, and event handler 390 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 388 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 376 creates and updates data used inapplication 340-1. For example, data updater 376 stores a video fileused by media player module 344. In some embodiments, object updater 377creates and updates objects used by application 340-1. For example,object updater 377 creates a new user-interface object or updates theposition of a user-interface object. GUI updater 378 updates the GUI.For example, GUI updater 378 prepares display information and sends itto graphics module 332 for display on display system 312 (e.g., primarydisplay 102 of display portion 110, FIG. 1A and/or dynamic function row104, FIGS. 1A-1B).

In some embodiments, event handler(s) 390 includes or has access to dataupdater 376, object updater 377, and GUI updater 378. In someembodiments, data updater 376, object updater 377, and GUI updater 378are included in a single module of an application 340-1 or applicationview 391. In other embodiments, they are included in two or moresoftware modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate electronic device 300 withinput-devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc., on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 4 shows a block diagram of a peripheral electronic device 400, inaccordance with some embodiments. In some embodiments, peripheralelectronic device 400 is a peripheral input and output device that atleast partially contains a dynamic function row 104 and a physical inputmechanism, such as a set of physical keys (e.g., the set of physicalkeys 106, FIGS. 2A-2B) and/or a touchpad (e.g., touchpad 108, FIGS.2B-2C), within a same housing. Examples of peripheral electronic device400 includes: peripheral keyboard (e.g., peripheral keyboard 206, FIGS.2A-2B), a peripheral touch-sensitive surface (e.g., first peripheralinput mechanism 212, FIG. 2C), or other peripheral input mechanisms(e.g., second peripheral input mechanism 222, FIG. 2D). Peripheralelectronic device 400 is communicatively coupled with computing device202 (FIGS. 2A-2D). For example, peripheral electronic device 400 iscommunicatively coupled with computing device 202 via a wiredconnection, such as USB or PS/2, or via a wireless communication link,using a communication protocol such as Bluetooth, Wi-Fi, or the like.Peripheral electronic device 400 may rely on some of the components orprocedures in electronic device 300 (FIG. 3A) or some of thesecomponents or procedures may be completed by, located in, or housed byperipheral electronic device 400 instead of electronic device 300.

In some embodiments, peripheral electronic device 400 includes one ormore of memory 402 (which optionally includes one or more computerreadable storage mediums), memory controller 422, one or more processingunits (CPU(s)) 420, peripherals interface 418, RF circuitry 408, audiocircuitry 410, speaker 411, microphone 413, input/output (I/O) subsystem406, other input or control devices 416, and external port 424.Peripheral electronic device 400 includes a touch-sensitive displaysystem 412 (e.g., dynamic function row 104, FIGS. 2A-2D) (sometimes alsoherein called a “touch-sensitive display,” a “touch screen,” or a “touchscreen display”).

Peripheral electronic device 400 optionally includes one or moreintensity sensors 465 for detecting intensity of contacts on atouch-sensitive surface such as touch-sensitive display system 412 or atouchpad (e.g., touchpad 108, FIGS. 2B-2C). Peripheral electronic device400 optionally includes one or more tactile output generators 467 forgenerating tactile outputs on a touch-sensitive surface such astouch-sensitive display system 412 or a touchpad (e.g., touchpad 108,FIGS. 2B-2C). These components optionally communicate over one or morecommunication buses or signal lines 403.

Memory 402 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Access to memory 402 by othercomponents of peripheral electronic device 400, such as CPU(s) 420 andperipherals interface 418, is, optionally, controlled by memorycontroller 422. Peripherals interface 418 can be used to couple CPU(s)420 and memory 402 to I/O subsystem 406 and other circuitry. The one ormore processing units 420 run or execute various software programsand/or sets of instructions stored in memory 402 to perform variousfunctions for peripheral electronic device 400 and to process data. Insome embodiments, peripherals interface 418, CPU(s) 420, and memorycontroller 422 are, optionally, implemented on a single chip, such aschip 404. In some other embodiments, they are, optionally, implementedon separate chips.

RF (radio frequency) circuitry 408 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 408 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 408 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. Thewireless communication optionally uses any of a plurality ofcommunications standards, protocols and technologies, including but notlimited to near field communication (NFC), Bluetooth, Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, and/or IEEE802.11n), Wi-MAX, or any other suitable communication protocol,including communication protocols not yet developed as of the filingdate of this document.

Optional audio circuitry 410, speaker 411, and microphone 413 provide anaudio interface between a user and peripheral electronic device 400.Audio circuitry 410 receives audio data from peripherals interface 418,converts the audio data to an electrical signal, and transmits theelectrical signal to speaker 411. Speaker 411 converts the electricalsignal to human-audible sound waves. Audio circuitry 410 also receiveselectrical signals converted by microphone 413 from sound waves. Audiocircuitry 410 converts the electrical signals to audio data andtransmits the audio data to peripherals interface 418 for processing.Audio data is, optionally, retrieved from and/or transmitted to memory402 and/or RF circuitry 408 by peripherals interface 418. In someembodiments, audio circuitry 410 also includes a headset jack. Theheadset jack provides an interface between audio circuitry 410 andremovable audio input/output peripherals, such as output-only headphonesor a headset with both output (e.g., a headphone for one or both ears)and input (e.g., a microphone).

I/O subsystem 406 couples the input/output peripherals of peripheralelectronic device 400, such as touch-sensitive display system 412 (e.g.,dynamic function row 104, FIGS. 2A-2D), to peripherals interface 418.I/O subsystem 406 optionally includes display controller 456, intensitysensor controller 459, haptic feedback controller 461, and one or moreinput controllers 460 for other input or control devices 416. The one ormore other input controllers 460 receive/send electrical signals from/toother input or control devices 416. The other input or control devices416 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, a setof physical keys, a touchpad, and so forth.

Touch-sensitive display system 412 (e.g., dynamic function row 104,FIGS. 2A-2D) provides an input/output interface between peripheralelectronic device 400 and a user. Touch-sensitive display (TSD)controller 456 receives and/or sends electrical signals from/totouch-sensitive display system 412. Touch-sensitive display system 412displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output corresponds to user-interface objects/elements.

Touch-sensitive display system 412 (e.g., dynamic function row 104,FIGS. 2A-2D) includes a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. As such, touch-sensitive display system 412 and TSD controller456 (along with any associated modules and/or sets of instructions inmemory 402) detect contact (and any movement or breaking of the contact)on touch-sensitive display system 412 and convert the detected contactinto signals used to select or control user-interface objects (e.g., oneor more soft keys, icons, web pages, or images) that are displayed ontouch-sensitive display system 412. In one example embodiment, a pointof contact between touch-sensitive display system 412 and the usercorresponds to an area of touch-sensitive display system 412 in contactwith a finger of the user.

Touch-sensitive display system 412 (e.g., dynamic function row 104,FIGS. 2A-2D) optionally uses LCD (liquid crystal display) technology,LPD (light emitting polymer display) technology, LED (light emittingdiode) technology, or OLED (organic light emitting diode) technology,although other display technologies are used in other embodiments.Touch-sensitive display system 412 and TSD controller 456 optionallydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch-sensitive display system 412. In one example embodiment,projected mutual capacitance sensing technology is used, such as thatfound in the iPHONE®, iPODTOUCH®, and iPAD® from Apple Inc. ofCupertino, Calif.

Touch-sensitive display system 412 (e.g., dynamic function row 104,FIGS. 2A-2D) optionally has a video resolution in excess of 400 dpi(e.g., 500 dpi, 800 dpi, or greater). In some embodiments, the usermakes contact with touch-sensitive display system 412 using a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures.

In some embodiments, in addition to touch-sensitive display system 412,peripheral electronic device 400 optionally includes a touchpad (e.g.,touchpad 108, FIGS. 2B-2C). In some embodiments, the touchpad is atouch-sensitive area of peripheral electronic device 400 that, unliketouch-sensitive display system 412, does not display visual output. Insome embodiments, the touchpad is, optionally, a touch-sensitive surfacethat is separate from touch-sensitive display system 412, or anextension of the touch-sensitive surface formed by touch-sensitivedisplay system 412.

Peripheral electronic device 400 also includes power system 462 forpowering the various components. Power system 462 optionally includes apower management system, one or more power sources (e.g., battery,alternating current (AC), etc.), a recharging system, a power failuredetection circuit, a power converter or inverter, a power statusindicator (e.g., a light-emitting diode (LED)) and any other componentsassociated with the generation, management and distribution of power inportable devices.

Peripheral electronic device 400 optionally also includes one or morecontact intensity sensors 465 coupled with intensity sensor controller459 in I/O subsystem 406. Contact intensity sensor(s) 465 optionallyincludes one or more piezoresistive strain gauges, capacitive forcesensors, electric force sensors, piezoelectric force sensors, opticalforce sensors, capacitive touch-sensitive surfaces, or other intensitysensors (e.g., sensors used to measure the force (or pressure) of acontact on a touch-sensitive surface). Contact intensity sensor(s) 465receives contact intensity information (e.g., pressure information or aproxy for pressure information) from the environment. In someembodiments, at least one contact intensity sensor is collocated with,or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 412 and/or touchpad 108, FIGS. 2B-2C).

Peripheral electronic device 400 optionally also includes one or moretactile output generators 467 coupled with haptic feedback controller461 in I/O subsystem 406. Tactile output generator(s) 467 optionallyincludes one or more electroacoustic devices such as speakers or otheraudio components and/or electromechanical devices that convert energyinto linear motion such as a motor, solenoid, electroactive polymer,piezoelectric actuator, electrostatic actuator, or other tactile outputgenerating component (e.g., a component that converts electrical signalsinto tactile outputs on the device). Contact intensity sensor(s) 465receives tactile feedback generation instructions from haptic feedbackmodule 433 and generates tactile outputs that are capable of beingsensed by a user of peripheral electronic device 400. In someembodiments, at least one tactile output generator is collocated with,or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 412 and/or touchpad 108, FIGS. 2B-2C) and, optionally,generates a tactile output by moving the touch-sensitive surfacevertically (e.g., in/out of a surface of peripheral electronic device400) or laterally (e.g., back and forth in the same plane as a surfaceof peripheral electronic device 400).

In some embodiments, the software components stored in memory 402include operating system 426, communication module 428 (or set ofinstructions), contact/motion module 430 (or set of instructions), anddynamic function row module 450 (or sets of instructions). Furthermore,in some embodiments, memory 402 stores device state 457 including thedisplay state, indicating what views or other information occupy variousregions of touch-sensitive display system 412 (e.g., dynamic functionrow 104, FIGS. 2A-2D).

Operating system 426 includes various software components and/or driversfor controlling and managing general system tasks (e.g., memorymanagement, storage device control, power management, etc.) andfacilitates communication between various hardware and softwarecomponents.

Communication module 428 facilitates communication with other devices(e.g., computing device 202, FIGS. 2A-2D) over one or more externalports 424 and/or RF circuitry 408 and also includes various softwarecomponents for sending/receiving data via RF circuitry 408 and/orexternal port 424. External port 424 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.).

Contact/motion module 430 optionally detects contact withtouch-sensitive display system 412 and other touch sensitive devices(e.g., a touchpad or physical click wheel). Contact/motion module 430includes various software components for performing various operationsrelated to detection of contact, such as determining if contact hasoccurred (e.g., detecting a finger-down event), determining an intensityof the contact (e.g., the force or pressure of the contact or asubstitute for the force or pressure of the contact), determining ifthere is movement of the contact and tracking the movement across thetouch-sensitive surface (e.g., detecting one or more finger-draggingevents), and determining if the contact has ceased (e.g., detecting afinger-up event or a break in contact). Contact/motion module 430receives contact data from the touch-sensitive surface. Determiningmovement of the point of contact, which is represented by a series ofcontact data, optionally includes determining speed (magnitude),velocity (magnitude and direction), and/or an acceleration (a change inmagnitude and/or direction) of the point of contact. These operationsare, optionally, applied to single contacts (e.g., one finger contacts)or to multiple simultaneous contacts (e.g., “multitouch”/multiple fingercontacts). In some embodiments, contact/motion module 430 also detectscontact on a touchpad (e.g., touchpad 108, FIGS. 2B-2C).

In some embodiments, contact/motion module 430 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has selected or“clicked” on an affordance). In some embodiments at least a subset ofthe intensity thresholds are determined in accordance with softwareparameters (e.g., the intensity thresholds are not determined by theactivation thresholds of particular physical actuators and can beadjusted without changing the physical hardware of peripheral electronicdevice 400). For example, a mouse “click” threshold of a trackpad ortouch screen display can be set to any of a large range of predefinedthresholds values without changing the trackpad or touch screen displayhardware. Additionally, in some implementations a user of the device isprovided with software settings for adjusting one or more of the set ofintensity thresholds (e.g., by adjusting individual intensity thresholdsand/or by adjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

Contact/motion module 430 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap contact includes detecting a finger-down event followed by detectinga finger-up (lift off) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and in some embodimentsalso followed by detecting a finger-up (lift off) event.

Haptic feedback module 433 includes various software components forgenerating instructions used by tactile output generator(s) 467 toproduce tactile outputs at one or more locations on peripheralelectronic device 400 in response to user interactions with peripheralelectronic device 400.

Touch-bar management module 450 includes analogous components andfunctions in an equivalent fashion as the touch-bar management module350 described above. For the sake of brevity, therefore, detailsregarding operation of the touch-bar management module are not repeatedhere as the descriptions supplied above with respect to touch-barmanagement module 350 to the module 450 (and its components) as well.

In some embodiments, memory 402 includes event sorter 470 (e.g., inoperating system 426). In some embodiments, event sorter 470 performsthe same functions as event sorter 370 (FIG. 3B) and includes a subsetor superset of the modules, procedures, and instructions of event sorter370 (FIG. 3B). As such, event sorter 470 will not be described for thesake of brevity.

It should be appreciated that peripheral electronic device 400 is onlyan example and that peripheral electronic device 400 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 4 areimplemented in hardware, software, firmware, or a combination thereof,including one or more signal processing and/or application specificintegrated circuits.

Each of the above identified modules correspond to a set of executableinstructions for performing one or more functions described above andthe methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (i.e., sets of instructions) need notbe implemented as separate software programs, procedures or modules, andthus various subsets of these modules are, optionally, combined orotherwise re-arranged in various embodiments. In some embodiments,memory 402 optionally stores a subset of the modules and data structuresidentified above. Furthermore, memory 402 optionally stores additionalmodules and data structures not described above.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector,” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch-screen display thatenables direct interaction with user interface elements on thetouch-screen display, a detected contact on the touch-screen acts as a“focus selector,” so that when an input (e.g., a press input by thecontact) is detected on the touch-screen display at a location of aparticular user interface element (e.g., a button, window, slider orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch-screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch-screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact or a styluscontact) on the touch-sensitive surface, or to a substitute (proxy) forthe force or pressure of a contact on the touch-sensitive surface. Theintensity of a contact has a range of values that includes at least fourdistinct values and more typically includes hundreds of distinct values(e.g., at least 256). Intensity of a contact is, optionally, determined(or measured) using various approaches and various sensors orcombinations of sensors. For example, one or more force sensorsunderneath or adjacent to the touch-sensitive surface are, optionally,used to measure force at various points on the touch-sensitive surface.In some implementations, force measurements from multiple force sensorsare combined (e.g., a weighted average or a sum) to determine anestimated force of a contact. Similarly, a pressure-sensitive tip of astylus is, optionally, used to determine a pressure of the stylus on thetouch-sensitive surface. Alternatively, the size of the contact areadetected on the touch-sensitive surface and/or changes thereto, thecapacitance of the touch-sensitive surface proximate to the contactand/or changes thereto, and/or the resistance of the touch-sensitivesurface proximate to the contact and/or changes thereto are, optionally,used as a substitute for the force or pressure of the contact on thetouch-sensitive surface. In some implementations, the substitutemeasurements for contact force or pressure are used directly todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is described in units corresponding to thesubstitute measurements). In some implementations, the substitutemeasurements for contact force or pressure are converted to an estimatedforce or pressure and the estimated force or pressure is used todetermine whether an intensity threshold has been exceeded (e.g., theintensity threshold is a pressure threshold measured in units ofpressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be readily accessible by the user on a reduced-size devicewith limited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of the portable computing system 100). Forexample, a mouse “click” threshold of a trackpad or touch-screen displaycan be set to any of a large range of predefined thresholds valueswithout changing the trackpad or touch-screen display hardware.Additionally, in some implementations a user of the device is providedwith software settings for adjusting one or more of the set of intensitythresholds (e.g., by adjusting individual intensity thresholds and/or byadjusting a plurality of intensity thresholds at once with asystem-level click “intensity” parameter).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second intensity threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more intensity thresholds is used to determine whether or not toperform one or more operations (e.g., whether to perform a respectiveoption or forgo performing the respective operation) rather than beingused to determine whether to perform a first operation or a secondoperation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location (e.g.,a drag gesture), at which point the intensity of the contact increases.In this example, the characteristic intensity of the contact at the endlocation may be based on only a portion of the continuous swipe contact,and not the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmmay be applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

In some embodiments one or more predefined intensity thresholds are usedto determine whether a particular input satisfies an intensity-basedcriterion. For example, the one or more predefined intensity thresholdsinclude (i) a contact detection intensity threshold IT₀, (ii) a lightpress intensity threshold IT_(L), (iii) a deep press intensity thresholdIT_(D) (e.g., that is at least initially higher than I_(L)), and/or (iv)one or more other intensity thresholds (e.g., an intensity thresholdI_(H) that is lower than I_(L)). In some embodiments, the light pressintensity threshold corresponds to an intensity at which the device willperform operations typically associated with clicking a button of aphysical mouse or a trackpad. In some embodiments, the deep pressintensity threshold corresponds to an intensity at which the device willperform operations that are different from operations typicallyassociated with clicking a button of a physical mouse or a trackpad. Insome embodiments, when a contact is detected with a characteristicintensity below the light press intensity threshold (e.g., and above anominal contact-detection intensity threshold IT₀ below which thecontact is no longer detected), the device will move a focus selector inaccordance with movement of the contact on the touch-sensitive surfacewithout performing an operation associated with the light pressintensity threshold or the deep press intensity threshold. Generally,unless otherwise stated, these intensity thresholds are consistentbetween different sets of user interface figures.

In some embodiments, the response of the device to inputs detected bythe device depends on criteria based on the contact intensity during theinput. For example, for some “light press” inputs, the intensity of acontact exceeding a first intensity threshold during the input triggersa first response. In some embodiments, the response of the device toinputs detected by the device depends on criteria that include both thecontact intensity during the input and time-based criteria. For example,for some “deep press” inputs, the intensity of a contact exceeding asecond intensity threshold during the input, greater than the firstintensity threshold for a light press, triggers a second response onlyif a delay time has elapsed between meeting the first intensitythreshold and meeting the second intensity threshold. This delay time istypically less than 200 ms in duration (e.g., 40, 100, or 120 ms,depending on the magnitude of the second intensity threshold, with thedelay time increasing as the second intensity threshold increases). Thisdelay time helps to avoid accidental deep press inputs. As anotherexample, for some “deep press” inputs, there is a reduced-sensitivitytime period that occurs after the time at which the first intensitythreshold is met. During the reduced-sensitivity time period, the secondintensity threshold is increased. This temporary increase in the secondintensity threshold also helps to avoid accidental deep press inputs.For other deep press inputs, the response to detection of a deep pressinput does not depend on time-based criteria.

In some embodiments, one or more of the input intensity thresholdsand/or the corresponding outputs vary based on one or more factors, suchas user settings, contact motion, input timing, application running,rate at which the intensity is applied, number of concurrent inputs,user history, environmental factors (e.g., ambient noise), focusselector position, and the like. Example factors are described in U.S.patent application Ser. Nos. 14/399,606 and 14/624,296, which areincorporated by reference herein in their entireties.

For example, FIG. 3C illustrates a dynamic intensity threshold 480 thatchanges over time based in part on the intensity of touch input 476 overtime. Dynamic intensity threshold 480 is a sum of two components, firstcomponent 474 that decays over time after a predefined delay time p1from when touch input 476 is initially detected, and second component478 that trails the intensity of touch input 476 over time. The initialhigh intensity threshold of first component 474 reduces accidentaltriggering of a “deep press” response, while still allowing an immediate“deep press” response if touch input 476 provides sufficient intensity.Second component 478 reduces unintentional triggering of a “deep press”response by gradual intensity fluctuations of in a touch input. In someembodiments, when touch input 476 satisfies dynamic intensity threshold480 (e.g., at point 481 in FIG. 3C), the “deep press” response istriggered.

FIG. 3D illustrates another dynamic intensity threshold 486 (e.g.,intensity threshold I_(D)). FIG. 3D also illustrates two other intensitythresholds: a first intensity threshold I_(H) and a second intensitythreshold I_(L). In FIG. 3D, although touch input 484 satisfies thefirst intensity threshold I_(H) and the second intensity threshold I_(L)prior to time p2, no response is provided until delay time p2 haselapsed at time 482. Also in FIG. 3D, dynamic intensity threshold 486decays over time, with the decay starting at time 488 after a predefineddelay time p1 has elapsed from time 482 (when the response associatedwith the second intensity threshold I_(L) was triggered). This type ofdynamic intensity threshold reduces accidental triggering of a responseassociated with the dynamic intensity threshold I_(D) immediately after,or concurrently with, triggering a response associated with a lowerintensity threshold, such as the first intensity threshold I_(H) or thesecond intensity threshold I_(L).

FIG. 3E illustrate yet another dynamic intensity threshold 492 (e.g.,intensity threshold I_(D)). In FIG. 3E, a response associated with theintensity threshold I_(L) is triggered after the delay time p2 haselapsed from when touch input 490 is initially detected. Concurrently,dynamic intensity threshold 492 decays after the predefined delay timep1 has elapsed from when touch input 490 is initially detected. So adecrease in intensity of touch input 490 after triggering the responseassociated with the intensity threshold I_(L), followed by an increasein the intensity of touch input 490, without releasing touch input 490,can trigger a response associated with the intensity threshold I_(D)(e.g., at time 494) even when the intensity of touch input 490 is belowanother intensity threshold, for example, the intensity threshold I_(L).

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold IT_(L) to an intensity betweenthe light press intensity threshold IT_(L) and the deep press intensitythreshold IT_(D) is sometimes referred to as a “light press” input. Anincrease of characteristic intensity of the contact from an intensitybelow the deep press intensity threshold IT_(D) to an intensity abovethe deep press intensity threshold IT_(D) is sometimes referred to as a“deep press” input. An increase of characteristic intensity of thecontact from an intensity below the contact-detection intensitythreshold IT₀ to an intensity between the contact-detection intensitythreshold IT₀ and the light press intensity threshold IT_(L) issometimes referred to as detecting the contact on the touch-surface. Adecrease of characteristic intensity of the contact from an intensityabove the contact-detection intensity threshold IT₀ to an intensitybelow the contact-detection intensity threshold IT₀ is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments IT₀ is zero. In some embodiments, IT₀ is greaterthan zero. In some illustrations a shaded circle or oval is used torepresent intensity of a contact on the touch-sensitive surface. In someillustrations, a circle or oval without shading is used represent arespective contact on the touch-sensitive surface without specifying theintensity of the respective contact.

In some embodiments, described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., the respective operation is performed on a“down stroke” of the respective press input). In some embodiments, thepress input includes an increase in intensity of the respective contactabove the press-input intensity threshold and a subsequent decrease inintensity of the contact below the press-input intensity threshold, andthe respective operation is performed in response to detecting thesubsequent decrease in intensity of the respective contact below thepress-input threshold (e.g., the respective operation is performed on an“up stroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., the respective operationis performed on an “up stroke” of the respective press input).Similarly, in some embodiments, the press input is detected only whenthe device detects an increase in intensity of the contact from anintensity at or below the hysteresis intensity threshold to an intensityat or above the press-input intensity threshold and, optionally, asubsequent decrease in intensity of the contact to an intensity at orbelow the hysteresis intensity, and the respective operation isperformed in response to detecting the press input (e.g., the increasein intensity of the contact or the decrease in intensity of the contact,depending on the circumstances).

For ease of explanation, the description of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting: an increase in intensityof a contact above the press-input intensity threshold, an increase inintensity of a contact from an intensity below the hysteresis intensitythreshold to an intensity above the press-input intensity threshold, adecrease in intensity of the contact below the press-input intensitythreshold, or a decrease in intensity of the contact below thehysteresis intensity threshold corresponding to the press-inputintensity threshold. Additionally, in examples where an operation isdescribed as being performed in response to detecting a decrease inintensity of a contact below the press-input intensity threshold, theoperation is, optionally, performed in response to detecting a decreasein intensity of the contact below a hysteresis intensity thresholdcorresponding to, and lower than, the press-input intensity threshold.As described above, in some embodiments, the triggering of theseresponses also depends on time-based criteria being met (e.g., a delaytime has elapsed between a first intensity threshold being met and asecond intensity threshold being met).

User Interfaces and Associated Processes

Attention is now directed towards embodiments of user interfaces (“UIs”)and associated processes that may be implemented by portable computingsystem 100 (FIG. 1A) or desktop computing system 200 (FIGS. 2A-2D). Insome embodiments, primary display 102 is implemented in display portion110 of portable computing system 100 (FIG. 1A). Alternatively, in someembodiments, primary display 102 is implemented in peripheral displaydevice 204 (FIGS. 2A-2D). In some embodiments, dynamic function row 104is a touch-sensitive secondary display implemented in body portion 120of portable computing system 100 (FIGS. 1A-1B). Alternatively, in someembodiments, dynamic function row 104 is a touch-sensitive secondarydisplay implemented in peripheral keyboard 206 (FIGS. 2A-2B), firstperipheral input mechanism 212 (FIG. 2C), or second peripheral inputmechanism 222 (FIG. 2D).

FIGS. 5A-5AT are schematics of primary and secondary displays used toillustrate example user interfaces for customizing display modes for asecondary display and for interacting with a management user interfacefor the secondary display, in accordance with some embodiments. The userinterfaces in these figures are used to illustrate the methods and/orprocesses described below, including the methods in FIGS. 6A-6D and7A-7F. One of ordinary skill in the art will appreciate that thefollowing user interfaces are merely examples. Moreover, one of ordinaryskill in the art will appreciate that a different layout with additionalor fewer affordances, user interface elements, or graphics may be usedin practice.

FIG. 5A illustrates primary display 102 displaying a user interface 516that allows a user to associate various display modes for atouch-sensitive secondary display (also referred to herein as a “touchbar”), to select which touch bar display modes are available, and tocreate new touch bar display modes. In this description, the userinterface 516 is referred to as a touch-bar management user interface.

FIGS. 5A-5AT also illustrate that a biometric sensor 105 (e.g., afingerprint sensor 105) can be positioned adjacent to thetouch-sensitive display 104 in certain embodiments. This biometricsensor 105 may be included within a same housing that at least partiallycontains the secondary display 104 and a set of keyboard keys 106.

As is explained in more detail below, at various points in time, theremay be different display modes for the touch bar that are available foruse system-wide (referred to as “available display modes” or “availabletouch bar display modes”) based on which checkboxes are checked withinthe touch-bar management user interface (e.g., checkboxes 522 to 532 inuser interface 516, FIG. 5A), one of these available display modes willbe a current system-wide default display mode (referred to as the“system-wide default display mode”) that is set based on a systemdefault setting or based on an explicit request to change thesystem-wide default display mode, and respective applications may eachbe associated by a user with one of the available display modes (e.g.,using the user interface portion 520, FIG. 5A). In some embodiments, thesystem default setting for the system-wide default display mode is anadaptive display mode in which user interface elements are displayedwithin the touch bar based on a current state of a user interface thatis in focus on the primary display, and this system default display modesetting may be changed to define a new system-wide default display modeby providing a mode-switching input (e.g., by pressing a function key ata keyboard) and selecting the new system-wide default display mode(e.g., a user can toggle between display modes on the secondarydisplay).

For ease of explanation, some of the FIGS. 5A-5AT indicate a displaymode in which the secondary display 104 is currently operating. Forexample, FIG. 5AI has a parenthetical next to reference numeral 104 toindicate that the secondary display 104 is currently operating in aworkflows/macros display mode. Other of the FIGS. 5A-5AT include similarexplanatory parentheticals.

In FIG. 5A, a first portion 518 of the touch-bar management userinterface 516 allows a user to select the available display modes.Selecting a checkbox within this first portion 518 causes an associatedtouch-bar display mode to be included with the available display modes,which ensures that the associated touch-bar display mode is availablesystem-wide for any application that is compatible with the associatedtouch-bar display mode. For example, as pictured in FIG. 5B, selectingthe checkbox 522 using an input 538 causes the “dynamic app controls”touch-bar display mode to be made available system-wide for use withcompatible applications (i.e., any application that supports use of thedynamic app controls display mode by exchanging information with anoperating system to allow for dynamic updating of affordances displayedwith the secondary display as a state of the application changes).

FIG. 5A also shows that the touch-bar management user interface 516includes a second portion 520 adjacent to the first portion 518, thesecond portion 520 allows a user to associate individual applicationswith a particular touch bar display mode of the available touch bardisplay modes (e.g., only those display modes for which an associatedcheckbox has been checked within the first portion 518 are available tobe associated with applications). As to creation of new touch bardisplay modes, such functionality is offered by selecting the button 534that, when selected, initiates a process for creating a new touch bardisplay mode (as is explained in more detail below).

In some embodiments, one or more of the checkboxes shown in the firstportion 518 may be greyed-out, such that the system always ensures thatat least one display mode will be available for the touch-sensitivesecondary display 104 (e.g., this prevents users from disabling alldisplay modes for the secondary display 104). As an example, in someembodiments, the checkbox 522 is greyed-out, so that users are unable todeselect the dynamic app controls display mode. As another example, insome embodiments, the checkbox 532 is greyed-out, so that users areunable to deselect the function keys display mode. In some otherembodiments, both of the checkboxes 522 and 532 are greyed-out.

FIG. 5B shows an example of a user selecting as an available displaymode a single touch bar display mode by checking checkbox 522 using userinput 538. Next, FIG. 5C shows that the user has selected all checkboxes522, 524, 526, 528, 530, and 532 thereby causing each of the touch bardisplay modes associated therewith to added as available display modes.FIG. 5D also shows that a user can un-check certain checkboxes(checkboxes 528, 530, and 532 in the example illustrated in FIG. 5D havebeen un-checked using a series of inputs 542) to remove the displaymodes associated therewith from being included as available displaymodes (e.g., “text entry,” “expanded control strip,” and “function keys”display modes are removed from being available system-wide in theexample of FIG. 5D).

Turning to FIG. 5E-1, the user has selected, using input 544, the “+”affordance shown within second portion 520 of the touch-bar managementuser interface. In response to this selection, an overlay window 517 isdisplayed on the primary display 102, as is shown in FIG. 5E-2. Theoverlay window 517 allows the user to select an application, which isthen included within the second portion 520 of the touch-bar managementuser interface 516. For example, as shown in FIG. 5E-2, the userselects, using input 545, a user interface element associated with aMail application from within the overlay window 517.

Then, FIG. 5E-3 shows that the mail application is included within thesecond portion 520 of the touch-bar management user interface, alongwith either no display mode (i.e., it still needs to be selected by theuser) or a default display mode with which the mail application is nowassociated. For example, as shown in FIG. 5E-3, the default display modeis dynamic app controls, and that default mode is now associated withthe mail application (in some other embodiments, discussed below inreference to FIGS. 5T-1 to 5T-4, users may choose a display mode toassociate with the selected application directly within an alternativeimplementation of the overlay window 517). The association between themail application and the dynamic app controls display mode ensures thatwhen the mail application is opened, the secondary display is alsooperated in the dynamic app controls display mode.

Users are also able to easily switch which display mode is associatedwith each of the applications that are included within the secondportion 520. For example, as shown in FIG. 5F, the user is able toprovide input 546 at the downward pointing caret icon, which then causesthe display mode to change to a user shortcuts display mode instead ofthe previously-associated dynamic app controls display mode.

FIG. 5G illustrates that a user input 547 is provided at an affordance510 associated with an application that has not been associated with anyindividual display modes (in this example, a music player application).In response to this input, in FIG. 5H, the music player application 548is displayed on the primary display 102. In conjunction with displayingthe music player application 548, the secondary display 104 continues tooperate in the dynamic app controls mode (the music player applicationhas not been individually associated with a touch-bar display mode, sothe current system-wide default display mode is used), in which at leasta portion of the secondary display 104 is updated to displayapplication-specific affordances for the music player application (e.g.,the secondary display 104 now displays affordances for “Album A,” AlbumB,” and “Party Shuffle,” each of which controls functions availablewithin the music player application.

In FIG. 5H, the user has also selected “Podcasts” (using input 547) toswitch which library is displayed within the music player application.In response to the input 547, Figure SI shows that the music playerapplication displayed on primary display 102 has been updated to showrepresentations of various podcasts and the touch-sensitive secondarydisplay 104 has been updated to display affordances associated with atleast some of these representations. In other words, because thesecondary display 104 is operating in the dynamic app controls displaymode, the affordances displayed within the secondary display 104 changeas a state of the user interface displayed on the primary display 102changes.

As discussed herein, some users prefer to have display modes for thetouch-sensitive secondary display 104 that do not change based on theapplication's (or an associated user interface's) state. As such, theembodiments described herein allow users to associate certainapplications with persistent display modes for the touch-sensitivesecondary display, and also allow users to easily switch betweenadaptive (e.g., a mode like the dynamic app controls mode discussedabove) and persistent display modes (e.g., a mode like the usershortcuts display mode discussed below).

In FIG. 5J, the user has provided a mode-switching input the causesselectable options 552, 554, 556 for each available display mode for thesecondary display to be displayed (either on the secondary display 104,as shown in FIG. 5J-5K, on the primary display 102 as shown in FIG. 5M,or on a combination of both displays as shown in FIG. 5L). For example,in some embodiments, the mode-switching input (e.g., input 595) is apress of a function key on a keyboard (e.g., a keyboard with keys 106that is located adjacent to the touch-sensitive secondary display) and,in response, selectable options for each of the available display modesare then displayed.

Turning to 5K, while the mode-switching input is still being provided(e.g., input 595 at the illustrated function key of the keys 106, FIG.5K), the user then selects one of the selectable options for theavailable display modes, e.g., the selectable option 556 for theworkflows/macros display mode, using input 558, as is shown in FIG. 5K.In embodiments in which the available options are displayed on theprimary display (alternatively or in addition to the display on thesecondary display), then the user can also select one of the selectableoptions on the primary display (e.g., selecting selectable option 564using input 566, as is shown in FIG. 5M).

In response to the mode-switching input and to selection of one of theselectable options, the secondary display is then switched to operate inthe selected new display mode (e.g., the workflows/macros display modein the present example) and the selected new display mode replaces thedynamic app controls mode as the current system-wide default displaymode for the touch-sensitive secondary display. For example, in FIG. 5N,the secondary display 104 is switched to operate in the workflows/macrosdisplay mode. As pictured, the workflows/macros display mode includes afirst user interface element 5602 that, when selected, causes the systemto execute an associated workflow (e.g., to take a screenshot of theprimary display and to then attach that screen to an email, all inresponse to one click at the user interface element 5602); a second userinterface element 5604 that, when selected, causes the system to executean associated workflow (e.g., to save a current window to file and toplace that saved file on the desktop, all in response to one click atthe user interface element 5604).

As shown in FIGS. 5N-5P, the user may then provide inputs at the primarydisplay and the secondary display will continue to operate in theworkflows/macros display mode until the user either changes the currentsystem-wide default display mode or the user switches to an applicationthat has been associated with some other display mode. For example, inFIG. 5N, the user provides input 586 selecting a web browser icon and,in response, the primary display is updated to display a user interfacefor the web browser application (FIG. 5O) and the secondary displaystill continues to operate in the workflows/macros display mode.Additionally, users may provide inputs within individual applicationsand the touch bar will continue to operate in the workflows/macrosdisplay mode (e.g., as shown in FIG. 5P, the user provides an input 590to open a Website A and, in response, the primary display is updated todisplay content for website A and the secondary display 104 continues tooperate in the workflows/macros display mode).

Similarly, the user may also switch back to the music player application(e.g., by providing input 593 at the primary display) and the secondarydisplay will continue to operate in the text entry display mode (FIGS.5P-5Q).

In this way, users are able to quickly switch to a desired display modefor the secondary display and have that selection remain even as theyswitch between applications and switch what content is displayed withinindividual applications.

In some embodiments, if an application is specifically associated with aparticular display mode for the secondary display 104, then thatassociation will override the user's prior selection of theworkflows/macros display mode.

For example, with reference to FIG. 5Q, the user provides an input 594to launch an application that has been specifically associated with aparticular display mode (e.g., the input 594 corresponds to a request tolaunch the mail application, which was previously associated in themanagement user interface 516 with a user shortcuts display mode) and,in response, the secondary display switches to the particular displaymode (e.g., as shown in FIG. 5R, the secondary display 104 is nowoperated in the user shortcuts display mode). As depicted in FIG. 5R, insome embodiments, the user shortcuts display mode includes userinterface elements 5603, 5605 that each correspond to user-selectedshortcuts, so that users may provide a single input at the touch barinstead of having to recall and use complicated keyboard shortcuts.

FIG. 5R also illustrates that switching back to an application that isnot specifically associated with a particular display mode (e.g.,providing input 5010 to launch the web browser application, which hasnot been specifically associated with a particular display mode usingthe management user interface 516), will cause the current system-widedisplay mode to be chosen for the secondary display 104 (e.g., theworkflows/macros display mode is then used for the secondary display104, as shown in FIG. 5S).

Next, with reference to FIG. 5T, the user has opened the touch-barmanagement user interface 516, which is shown on the primary display102. FIG. 5T shows the user providing an input 5012 at the “+”affordance to allow for adding an additional application to the secondportion 520 of the touch-bar management user interface 516. In responseto the input 5012, the overlay window 517 is displayed, and the userselects to add the web browser application to the second portion 520using input 547.

In some embodiments, the web browser application is added to the secondportion 520 in response to the input 547 and is associated with adefault display mode, as was previously discussed with respect to FIGS.5E-1 to 5E-3. In other embodiments, and as shown in FIGS. 5T-1 to 5T-4,users are able to select the web browser application (e.g., using aninput 545, FIG. 5T-2) and to also select an associated display modedirectly within the overlay window 517 (e.g., using inputs 545-A and545-B, FIGS. 5T-3 and 5T-4). Then, as shown in FIG. 5U, the web browserapplication and the display mode that was selected to be associatedtherewith are both shown within the second portion 520 of the touch-barmanagement user interface 516 (e.g., user interface elements 5014 and5016 have been added to the second portion 520).

Users may also define new display modes for the touch-sensitivesecondary display 104, as is shown in FIGS. 5W-5AF, in which the usercreates a new display mode after providing an input 5018 at button 534(FIG. 5V), drags a variety of different user interface elements towithin the secondary display 104 (FIGS. 5W-5AE), and then names the newdisplay mode “Browser+Workspaces” (FIGS. 5AE-5AF). After creation ofthis new display mode, it is available for selection within the firstportion 518 of the touch-bar management user interface 516 (and may beselected using an input 5072 to make it available system-wide tocompatible applications), and may also be associated with an applicationthat has been added to the second portion 520.

For example, as shown in FIG. 5AH, in response to an input 5074, the webbrowser application may be associated with the new display mode, as ispictured in FIG. 5AI. After this association has been established, thenan input to open the web browser application (e.g., input 5076, FIG.5AI) causes the secondary display to operate in the new display mode(e.g., in FIG. 5AJ the secondary display is operated in the new displaymode, Browser+Workspaces).

Shifting to another application (e.g., mail application after input 5078over an icon for the mail application, FIG. 5AJ causes the mailapplication to then be displayed in FIG. 5AK). Once the mail applicationis opened, the secondary display is operated in the workflows/macrosdisplay mode (FIG. 5AK) as the workflows/macros display mode is thecurrent system-wide display mode for the secondary display.

In Figure SAL, the user has opened the touch-bar management userinterface and proceeds to deselect checkbox 522 (FIG. 5AM) and todeselect, checkbox 526 (FIG. 5AN), leaving just two display modesincluded with the available display modes as is shown in FIG. 5AO. FIG.5AN also shows that, in some embodiments, when a request is received toremove the current system-wide default display mode from the availabledisplay modes (e.g., deselection of the checkbox 526 in FIG. 5AN), thena new system-wide default display mode is automatically (without anyother user input) selected by the system. In this example, the usershortcuts display mode is selected as the new system-wide defaultdisplay mode and, accordingly, the secondary display is switched tooperate in the user shortcuts display mode in FIG. 5AN.

FIG. 5AO also shows that the user requests (via input 5084) to open themusic player application, which is then opened in response to the input5084 in FIG. 5AP.

In some embodiments, when just two display modes are available forsystem-wide usage, then providing the mode-switching input discussedabove causes the display mode for the secondary display to togglebetween these two display modes (instead of requiring the user toprovide an additional input to select a desired display mode). Forexample, as shown in FIGS. 5AP and 5AQ, the user provides themode-switching input (e.g., pressing a function key with input 583 at akeyboard with keys 106 that are adjacent to the secondary display 104)and, in response, the secondary display now shows representations of thetwo available display modes and a focus selector (grey highlightingdepicted in FIG. 5AQ) is placed on the first representation associatedthe browser+workspaces display mode as that will be the currentsystem-wide default display mode. The display mode of the secondarydisplay 104 also switches from the user shortcuts display mode and tothe browser+workspaces display mode, as is shown in FIG. 5AR.

In some embodiments, the system moves directly from FIG. 5AP to FIG.5AR, and does not display representations of the two available displaymodes on the secondary display, instead the system just directly togglesbetween the two available display modes.

FIG. 5AR additionally shows that a user may select the active workspacesaffordance within the secondary display (e.g., by providing input 579)and, in response, the secondary display 104 and the primary display 102are updated to include representations of the user's active workspaces(FIG. 5AS).

In certain embodiments, instead of having an active workspaces button,such as that shown in FIG. 5AR, the user may be able to use a missioncontrol mode for the secondary display 104, in which representations ofa user's active workspaces are persistently displayed within thesecondary display 104. This mission control mode can be one of thedisplay modes shown with associated checkboxes in the first portion 518of the touch-bar management user interface 516.

FIG. 5AS shows an embodiment of a mission control mode that is displayedin response to selection of the active workspaces affordance from withinthe secondary display 104 or in response to launching an applicationthat has been associated with the mission control mode. Once invoked bya user, the system displays one or more user interface elements eachrepresenting (e.g., via a miniaturized screenshot) a respective opendesktop including its respective open and unhidden user interfaces orwindows. In some embodiments, the one or more affordances 5502 of theopen desktops are displayed on the secondary display 104. In otherembodiments, the one or more affordances 5501 of the open desktops aredisplayed on the primary display 102. In yet other embodiments, the oneor more affordances of the open desktops are displayed on both theprimary 102 and secondary 104 displays.

In some embodiments, for the mission control mode and the user actionmode, the user can long press (or deep press by applying more pressurewith the input 579 depicted in FIG. 5AS) on a mission control affordanceon the secondary display to display the one or more affordances of theopen desktops on the secondary display (representations of the currentlyactive spaces or desktops for the mission control mode (as is depictedin FIG. 5AS) or representations of the user actions for the user actionmode). Once these affordances are displayed on the secondary display,the user can directly select one of these affordances to switch to thatdesktop/space or user action, or drag a finger over the affordances andlift-off to select the affordance under the user's finger (e.g., asshown in FIG. 5AS, the user lift-off while the input 579 is overaffordance 5502-C and, in response, the workspace corresponding toaffordance 5502-C is then displayed on the primary display for workspace5501-C in FIG. 5AT).

Additional descriptions regarding FIGS. 5A-5AT are provided below inreference to methods 600-700.

FIGS. 6A-6D are a flowchart of a method 600 of using customized displaymodes for touch-sensitive secondary displays, in accordance with someembodiments. The method 600 is performed (602) at a computing systemincluding one or more processors, memory, a first housing including aprimary display, and a second housing at least partially containing atouch-sensitive secondary display that is distinct from the primarydisplay. Some operations in method 600 are, optionally, combined and/orthe order of some operations is, optionally, changed.

In some embodiments, the computing system is portable computing system100 (FIG. 1A) or desktop computing system 200 (FIGS. 2A-2D). In someembodiments, the primary display is primary display 102 (FIG. 1A) whichis implemented in display portion 110 (also referred to herein as afirst housing 110 that includes the primary display 102) of portablecomputing system 100 (FIG. 1A) and the second housing is a body portion120 of the portable computing system 100, and the second housing atleast partially contains the touch-sensitive secondary display (e.g.,dynamic function row 104, FIGS. 1A-1B) and a physical keyboard (e.g.,the set of physical keys 106) (604).

In some embodiments, the second housing is not connected to the firsthousing (606), e.g., because the first housing is part of a first deviceand the second housing is part of a different device other than thefirst device (e.g., the second housing could be part of a mobile phone,a tablet device, or any other device that includes affordances that aredisplayed on a smaller secondary display while that other device isconnected to a computing system that includes a larger primary display).As one non-limiting example, in some embodiments, the second housing isperipheral keyboard 206 (FIGS. 2A-2B) of desktop computing system 200,which at least partially contains the touch-sensitive secondary display(e.g., dynamic function row 104, FIGS. 2A-2B) and the physical keyboard(e.g., the set of physical keys 106, FIGS. 2A-2B). As another example,in some embodiments, the second housing is first peripheral inputmechanism 212 (FIG. 2C) of desktop computing system 200, which at leastpartially contains the touch-sensitive secondary display (e.g., dynamicfunction row 104, FIG. 2C) and the second housing includes an inputmechanism (e.g., touchpad 108, FIG. 2C) and does not include thephysical keyboard. As one more example, in some embodiments, thesecondary display is a narrow, rectangular OLED display that ispositioned adjacent to a physical keyboard, such as the Touch Bar madeby APPLE INC. of Cupertino, Calif. In other embodiments, the secondarydisplay is any device that includes a smaller display than that of theprimary display (e.g., the secondary display is a smart watch).)

As described below, the method 600 (and associated interfaces) enablesuse of customized display modes for touch-sensitive secondary displays.As shown in FIG. 6A, the method 600 initially includes displaying (602),on the primary display, a first user interface for a first application(e.g., a first application window for a music player application, as isshown in FIG. 5H), and the first user interface is in focus on theprimary display. In this example, the first application has not beenassociated by a user with any one particular touch-bar display mode (seediscussion below regarding use of a management user interface toassociate applications with specific touch-bar display modes), which isdepicted in FIG. 5G as the music player application is not includedwithin the list of applications (also referred to as the second portion520 of the touch-bar management user interface 516) that have beenindividually associated with a particular display mode. For the purposesof this disclosure, a user element “in focus” means that the userinterface element is going to receive user input that is provided at thecomputing system (e.g., keyboard presses will be sent to the userinterface that is in focus).

While the touch-sensitive secondary display is operating in an adaptivedisplay mode in which at least some application-specific user interfaceelements are adaptively selected for display on a respective portion ofthe touch-sensitive secondary display based on a current state of thefirst user interface for the application (604) (e.g., the adaptivedisplay mode is the current system-wide default display mode), themethod includes: displaying, on the respective portion of thetouch-sensitive secondary display, a plurality of application-specificuser interface elements that are selected based on the current state ofthe first user interface for the application; and receiving a request tooperate the touch-sensitive secondary display in a respective persistentdisplay mode for the touch-sensitive secondary display, and therespective persistent display mode is distinct from the adaptive displaymode. As an example, while the touch-sensitive secondary display 104 isoperating in the adaptive display mode in FIG. 5I, the plurality ofapplication-specific user interface elements shown in the secondarydisplay of FIG. 5I are selected as the music player application is in astate in which it is currently displaying available podcast selections.Additionally, FIG. 5J shows that the request to operate thetouch-sensitive display in a respective persistent display mode isreceived (e.g., a mode-switching input is received, such as a selectionof a function key on a keyboard, and a selection is made of one of theworkflows/macros display mode by tapping with input 558 on userinterface element 556 in FIG. 5K).

In some embodiments, while the secondary display is operating in theadaptive display mode, the touch-sensitive secondary display also (inaddition to the plurality of application-specific user interfaceelements) displays one or more system-level affordances that do notchange based on the current state of the application (e.g., only each ofthe app-specific affordances are adaptively selected and the one or moresystem-level affordances are continuously displayed in thetouch-sensitive secondary display, and examples of the one or moresystem-level affordances are the volume, brightness, and Siri controlsshown in FIG. 5I).

In response to receiving the request, the method includes operating(606) the touch-sensitive secondary display in the respective persistentdisplay mode (and ceasing to operate the touch-sensitive secondarydisplay in the adaptive display mode), including updating the respectiveportion of the touch-sensitive secondary display to display a fixed setof user interface elements associated with the respective persistentdisplay mode. For example, as shown in FIG. 5N, after the request isreceived to operate the secondary display 104 in the workflows/macrosdisplay mode, the secondary display 104 displays user interface elementsassociated with that display mode (e.g., user interface elements 5602,5604, and other user interface elements associated with other workflowtasks up to Workflow N). In some embodiments, the user interfaceelements 5602, 5604 are selected by a user when the user creates a newtouch-bar display mode (creating new touch-bar display modes isdescribed elsewhere in this description and, for brevity, those detailsare not repeated here).

After changing focus to a second user interface for a second application(e.g., after detecting a request to open a second application (such as auser selecting a UI window for the second app), so that the second userinterface for the second application then is in focus on the primarydisplay instead of the first user interface for the first application):displaying (608), on the primary display, the second user interface forthe second application; and maintaining display (608), on the respectiveportion (e.g., all) of the touch-sensitive secondary display, of thefixed set of user interface elements associated with the respectivepersistent display mode. An example of the request to open the secondapplication is shown in FIG. 5N, in which a user provides an input 586to launch a web browser application on the primary display and, inresponse to this input, (i) a second user interface for the secondapplication is displayed (e.g., a user interface 588 for the web browserapplication, FIG. 5O) and (ii) display of the same fixed set of userinterface elements that was displayed in FIG. 5N is maintained for thesecondary display 104 (FIG. 5O).

In some instances, users of computing systems are unable to change thedisplay mode of a touch-sensitive secondary display from an adaptivedisplay mode to a persistent display mode. In the adaptive display mode,application-specific user interface elements are selected by thecomputing system and displayed on the touch-sensitive secondary displaybased on a state of an application that is currently in focus, while inthe persistent display mode a fixed set of user interface elements iscontinuously/persistently displayed on the touch-sensitive secondarydisplay and the fixed set continues to be displayed even as the state ofthe application may change. Receiving a request from the user to operatein the predefined persistent display mode provides the user with aconvenient way to quickly switch to the persistent display mode.Providing this option to quickly switch between display modes enhancesoperability of the device and makes the human-machine interface moreefficient (e.g., by allowing the users to easily customize their use ofthe touch-sensitive secondary display without having to waste timemanually searching for desired user interface elements that may bedifficult to locate or may be unavailable based on certain states of theapplication).

In some embodiments, users are able to quickly switch between displaymodes for the secondary display by simply providing the requestdiscussed above (e.g., by providing a mode-switching input such as apress on a function key of a keyboard). Whether the secondary displaysimply toggles between available display modes or whether a user needsto select which display mode to switch to can depend on how many displaymodes are currently available display modes. For example, turning now toFIG. 6B and continuing from the “A” marker shown with operation 604 inFIG. 6A, the method also includes determining (609) a number ofavailable display modes for the touch-sensitive secondary display (e.g.,how many of the checkboxes within the first portion 518 of the touch-barmanagement user interface 516 are currently selected). In response toreceiving the request: in accordance with the determination at operation609 indicating that the touch-sensitive secondary display is associatedwith two available display modes for the touch-sensitive secondarydisplay (609-2 or less, such as is shown on FIG. 5AN), the methodincludes switching (610) from operating the touch-sensitive secondarydisplay in the adaptive display mode to operating the touch-sensitivesecondary display in the respective persistent display mode (e.g., inFIGS. 5AQ-5AR, in response to a mode-switching input the secondarydisplay toggles to a different display mode, such as from the usershortcuts display mode and switches to the browser+workspaces displaymode).

In some embodiments, this switching operation 610 is performed withoutreceiving additional input at either the touch-sensitive secondarydisplay or at the primary display, other than the mode-switching input.Therefore, display modes at the touch-sensitive secondary display are,optionally, switched between adaptive and persistent display modes usinga single key press (e.g., by pressing a function key at a keyboard) andwithout providing any other input). In some embodiments, when only twodisplay modes are available (e.g., just the predefined persistentdisplay mode and the adaptive display mode), then representations ofeach of the two display modes can still be displayed at the secondary orprimary display (e.g., as is shown in FIG. 5AQ), but no explicitselection of these display modes as needed as simply pressing thefunction key causes the secondary display to switch between the twodisplay modes. In some embodiments switching between the two displaymodes is permanent and continues after activation of the function keyends, with a second activation of the function key switching backbetween the two display modes. In some embodiments, switching betweenthe two display modes is temporary and only continues as long asactivation of the function key continues, and the device switches backto the original display mode in response to detecting an end ofactivation of the function key.

Switching from operating the touch-sensitive secondary display in theadaptive display mode to operating the touch-sensitive secondary displayin the predefined persistent display mode provides the user with aconvenient way to quickly switch between two display modes. Providingthis option enhances operability of the device and makes thehuman-machine interface more efficient (e.g., by helping the userseasily select the predefined display mode without wasting computingresources, and thereby allow the users to easily customize their use ofthe touch-sensitive secondary display without having to waste timemanually searching for desired display modes that may be difficult tolocate).

If there are three or more display modes available, then simply togglingmay be inefficient as users could more quickly select a desired displaymode from among the three or more available display modes. Referringback to FIG. 6B, in response to receiving the request and beforeoperating the touch-sensitive secondary display in the respectivepersistent display mode: in accordance with the determination atoperation 609 indicating that three or more display modes are availablefor the touch-sensitive secondary display (609-3 or more, an example ofwhich is depicted in FIG. 5F in which three display modes have beenselected as being available display modes), the method includesdisplaying (612) a plurality of user interface elements associated withavailable display modes (e.g., user interface elements 552, 554, and 556are shown in secondary display 104), including a first user interfaceelement associated with the respective persistent display mode (e.g.,user interface element 554, FIG. 5J), a second user interface elementassociated with the adaptive display mode (e.g., user interface element552, FIG. 5J), and a third user interface element associated with anadditional persistent display mode (e.g., user interface element 556,FIG. 5J). Receiving the request includes receiving a selection of arespective user interface element that is associated with the respectivepersistent display mode (e.g., a user taps on one the user interfaceelement 556 associated with the workflows/macros available display mode,FIG. 5K).

In some instances, there may be three or more display modes associatedwith the secondary display and users are unable to easily toggle betweenthese modes, without having to waste time navigating through complicatedmenu structures. Displaying user interface elements respectivelyassociated with each of the three or more display modes provides theuser with a convenient way to quickly select a predefined display modewhere there are three or more display modes to select from. Providingthis option to quickly select between display modes enhances operabilityof the device and makes the human-machine interface more efficient(e.g., by helping the users easily select the predefined display modewithout wasting computing resources, and thereby allow the users toeasily customize their use of either the primary display ortouch-sensitive secondary display without having to waste time manuallysearching for desired display modes that may be difficult to locate).

In some embodiments, the plurality of user interface elements associatedwith available display modes are displayed at the primary display (614).An example of this is shown in FIGS. 5L and 5M. Displaying the three ormore display mode options at the primary display provides the user witha convenient way to quickly select a display mode, while also being ableto easily view which modes are available. Providing this option toquickly select between display modes enhances operability of the deviceand makes the human-machine interface more efficient (e.g., by helpingthe users easily select the predefined display mode without wastingcomputing resources, and thereby allow the users to easily customizetheir use of the primary display or touch-sensitive secondary displaywithout having to waste time manually searching for desired displaymodes that may be difficult to locate).

Alternatively, or in addition to display of the plurality of userinterface elements at the primary display with operation 614, theplurality of user interface elements associated with available displaymodes are displayed at the touch-sensitive secondary display (616). Anexample of this is shown in FIGS. 5J, 5K, and 5L. Displaying the threeor more display mode options at the touch-sensitive secondary displayprovides the user with a convenient way to quickly select a displaymode. Providing this option to quickly select between display modesenhances operability of the device and makes the human-machine interfacemore efficient (e.g., by helping the users easily select the predefineddisplay mode without wasting computing resources, and thereby allow theusers to easily customize their use of the primary display ortouch-sensitive secondary display without having to waste time manuallysearching for desired display modes that may be difficult to locate).

In some embodiments, users can both provide the mode-switching input(e.g., pressing the function key at the keyboard) and also provide anadditional input to select which display mode to use for the secondarydisplay. For example, the request (e.g., provided via the mode-switchinginput) includes (618) activation of a key of a keyboard (e.g., afunction key on the keyboard) that is at least partially containedwithin the second housing that contains the touch-sensitive secondarydisplay (e.g., the touch-sensitive secondary display is positioned abovethe keyboard in the same plane as the keyboard, and the selection of therespective user interface element that is associated with the predefinedpersistent display mode is an additional input at the touch-sensitivesecondary display). In some embodiments, the additional input (e.g.,input 558, FIG. 5K) is used when the application is associated with 3 ormore display modes, and is not used when the application is associatedwith 2 or fewer display modes (instead providing the mode-switchinginput toggles the active display mode).

Providing for an additional input at the touch-sensitive secondarydisplay while the input remains in contact with a key of a keyboardduring the additional input provides the user with a convenient way toquickly invoke the available predefined display modes to select from.Providing this option to quickly select between display modes enhancesoperability of the device and makes the human-machine interface moreefficient (e.g., by helping the users easily select the predefineddisplay mode without wasting computing resources, and thereby allow theusers to easily customize their use of the primary display ortouch-sensitive secondary display without having to waste time manuallysearching for desired display modes that may be difficult to locate).

In some embodiments, the key is continuously activated during theadditional input (620). For example, as shown in FIG. 5K, the functionkey may be continuously activated while the user provides the additionalinput 558.

In some embodiments and as discussed previously, the key is amechanically-actuated key (622), e.g., a function key that ismechanically-actuated on the keyboard.

In some embodiments, in conjunction with the mode-switching input(and/or the additional input discussed above), a focus selector can bemoved between the plurality of user interface elements associated withthe available display modes. With reference now to FIG. 6C, in responseto receiving the request and before operating the touch-sensitivesecondary display in the respective persistent display mode (624):displaying user interface elements respectively associated with eachavailable display mode for the touch-sensitive secondary display,including a first user interface element associated with the adaptivedisplay mode (e.g., the first user interface element is the button shownin FIG. 5AQ with the text “user shortcuts”) and a second user interfaceelement associated with the predefined persistent display mode (e.g.,the second user interface element is the button shown in FIG. 5AQ withthe text “browser+workspaces”); and moving a focus selector from thefirst user interface element to the second user interface element (e.g.,the focus selector (providing a greyed background for the button) is nowover the second user interface element in FIG. 5AQ to provide a clearvisual cue that the browser+workspaces display mode will become theactive display mode for the touch bar).

Example embodiments of the fixed set of user interface elements that aredisplayed in the respective portion of the secondary display afteractivation of the respective persistent display mode are provided nextwith reference to FIG. 6C.

In one example, the fixed set of user interface elements associated withthe respective persistent display mode consists of (626) representationsof one or more shortcuts chosen by a user that, when selected at thetouch-sensitive secondary display, cause activation of a correspondingfunction associated with the respective shortcut. This is illustrated inFIG. 5AP in which the secondary display includes representations of oneor more shortcuts including a first representation 5603 of a firstshortcut for “switch apps,” a second representation 5605 of a secondshortcut for “force quit,” and other representations for other shortcutsuntil Shortcut N. Activation of any of these representations causesactivation of a corresponding function, e.g., activation of the firstrepresentation 5603 causes the system to perform a function of cyclingbetween open applications (which might otherwise require a sequence ofkeyboard inputs instead of a single input at the secondary display 104).In some instances, a user is unable to perform various functions due tothe high number of manual steps involved in performing the respectivefunctions. Including representations of one or more shortcuts selectedby a user as the display modes provides the user with a convenient wayto select a display mode that can quickly perform these respectivefunctions. This enhances operability of the device and makes thehuman-machine interface more efficient (e.g., by helping the userseasily perform functions without wasting computing resources, andthereby allow the users to easily customize their use of the devicewithout having to waste time manually performing the steps to carry outthe desired functions).

As another example, the fixed set of user interface elements associatedwith the respective persistent display mode consists of (628)representations of function keys chosen by a user that, when selected atthe touch-sensitive secondary display, cause activation of acorresponding function associated with the respective function key(e.g., examples of the default function keys include F1, F2, F3, etc.keys that are each associated with different functions assigned to thosekeys by a user or by the system). In some instances, a user is unable toutilize default function keys because the touch-sensitive secondarydisplay is operating in a display mode that does not include functionkeys. Including representations of function keys as the display modesprovides the user with a convenient way to select a display mode thatallows the user to utilize function keys. This enhances operability ofthe device and makes the human-machine interface more efficient (e.g.,by helping the users easily perform functions associated with thefunction keys without wasting computing resources, and thereby allow theusers to easily customize their use of the device without having towaste time manually performing the functions associated with thefunction keys).

As one more example, the fixed set of user interface elements associatedwith the respective persistent display mode consists of (630)representations of text-entry options chosen by a user that, whenselected at the touch-sensitive secondary display, cause a correspondingchange to text that is displayed on the primary display. For example,the representations of text-entry options can include a firstrepresentation of a text-entry option that causes bolding of selectedtext, a second representation of a text-entry option that causesitalicizing of selected text, etc. Examples of applications associatedwith text entry are word processing interfaces and the change to textthat is displayed optionally includes bolding text, italicizing text,adding text, adding an emoji, and any other text entry modifications. Insome instances, a user is unable to enter text at the touch-sensitivesecondary display. Including representations of applications associatedwith text entry as the display modes provides the user with a convenientway to select a display mode that allows the user to enter text at thetouch-sensitive secondary display. This enhances operability of thedevice and makes the human-machine interface more efficient (e.g., byhelping the users easily enter text at the touch-sensitive secondarydisplay without wasting computing resources, and thereby allow the usersto easily customize their use of the device).

In one additional example, the fixed set of user interface elementsassociated with the respective persistent display mode consists ofrepresentations of one or more automated tasks chosen by a user that,when selected at the touch-sensitive secondary display, cause activationof a corresponding series of functions associated with the respectiveautomated task. This is illustrated in FIG. 5AM in which representationsof a number of different automated tasks are shown within the secondarydisplay, including a first representation 5602 of a first automated taskfor taking a screenshot and adding that screenshot to an emailapplication (labelled as “screenshot+email” in FIG. 5AM), a secondrepresentation 5604 of a second automated task for saving a currentlyopen document to the user's desktop (labelled as “save to desktop” inFIG. 5AM), etc. to representation of Workflow N. Examples of the one ormore automated tasks can include macros, workflow routines (e.g.,AUTOMATOR routines such as those available on operating systems providedby APPLE INC. of Cupertino, Calif.), and other groupings of functionsthat allow users to perform multiple operations at once, based uponselection of a single user interface element. An example includes a usersetting up a workflow automator task that, based on selection of asingle representation at the touch bar, causes the computing system tocopy a currently displayed image, add it to an email, and then send theemail to a predefined list of email addresses (e.g., the user's familymembers). In some instances, a user is unable to perform variousfunctions due to the high number of manual steps involved in performingthe respective functions. Including representations of one or moremacros selected by a user as the display modes provides the user with aconvenient way to select a display mode that can quickly perform theserespective functions. This enhances operability of the device and makesthe human-machine interface more efficient (e.g., by helping the userseasily perform functions without wasting computing resources, andthereby allow the users to easily customize their use of the devicewithout having to waste time manually performing the steps to carry outthe desired functions).

In one final example, the fixed set of user interface elementsassociated with the respective persistent display mode arerepresentations of one or more system-level control options chosen by auser that, when selected at the touch-sensitive secondary display, causeactivation of a corresponding system-level function. The representationsof the one or more system-level control options may include a firstrepresentation of a first system-level control option (e.g., an optionfor controlling brightness at the primary display), a secondrepresentation of a second system-level control option (e.g., an optionfor controlling volume), etc.

Turning next to FIG. 6D, the method can optionally include: continuingto operate (636) the touch-sensitive secondary display in the respectivepersistent display mode until an additional request is received tooperate the touch-sensitive secondary display in a display mode otherthan the respective persistent display mode. In some embodiments, thepersistent display mode is only exited after an explicit request isreceived to switch to a different display mode. For example, theadditional request may include a user activating (e.g., tapping orpressing) a function key to toggle from the predefined persistentdisplay mode back to the adaptive display mode (if there are only 2display modes associated with the application, such as the examplediscussed above in reference to FIGS. 5AP-5AR). As another example, theadditional request may include the user activating (e.g., tapping orpressing) the function key and a user then selecting a representation ofthe adaptive display mode that is displayed within the secondary displayin response to the activation of the function key (if there are 3 ormore display modes associated with the application, then this examplemay apply, as is discussed above in reference to FIGS. 5I-5M).

In some instances, the touch-sensitive secondary display mode operatesin the predefined persistent display mode and the user is unable toswitch back to the adaptive display mode. Receiving an additionalrequest to operate the touch-sensitive secondary display in the adaptivedisplay mode allows the user to actively switch back to the adaptivedisplay mode. Providing this option enhances operability of the deviceand makes the human-machine interface more efficient (e.g., by helpingthe users easily select the predefined display mode without wastingcomputing resources, and thereby allow the users to easily customizetheir use of the touch-sensitive secondary display without having towaste time manually searching for desired display modes that may bedifficult to locate).

FIG. 6D also shows that the method also optionally includes, while thetouch-sensitive secondary display is operating in the respectivepersistent display mode (638): in accordance with determining that focushas changed to a third user interface for a different application, thedifferent application being associated with a user-selected display modefor the touch-sensitive secondary display: ceasing to operate thetouch-sensitive secondary display in the respective persistent displaymode and instead operating the touch-sensitive secondary display in theuser-selected display mode. For example, as is shown in FIG. 5AI, theuser provides a request to launch the web browser application usinginput 5076 and, in response, in FIG. 5AJ, focus changes to the thirduser interface for the different application (in this example thebrowsing interface for the web browser application). Based on this focuschange, the secondary display 104 is then operated in the user-selecteddisplay mode that was previously associated with the web browserapplication, which is the browser+workspaces display mode that wasassociated with the web browser application in FIGS. 5AG-5AI.

In some instances, while the touch-sensitive secondary display modeoperates in the predefined persistent display mode, a third applicationis opened. But the third application has been specifically associated(e.g., using the management UI discussed below) with a display mode thatis distinct from the predefined persistent display mode. Detecting anadditional request to open the third application overrides thepredefined persistent display mode by displaying the third applicationin the display mode associated with the third application. This functionenhances operability of the device and makes the human-machine interfacemore efficient (e.g., by automatically, and without input from theusers, using a display mode that has been specifically associated withthe third application, thereby allowing users to customize their use ofthe secondary display to suit their preferences and helping users toavoid wasting time having to manually switch to their preferred displaymode every time they open (or are using) the third application).

It should be understood that the particular order in which theoperations in FIGS. 6A-6D have been described is merely one example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

The touch bar interface allows users to (i) choose a plurality of modesin which the touch bar can operate, and (ii) allow users to assignparticular touch bar modes to particular applications. As described atleast partially above, the tough bar can operate in a plurality ofavailable touch bar modes, including without limitation, a dynamicapplication mode, a user shortcuts mode, a workflows or macros mode, atext entry mode, an expanded control strip mode, a default function keysmode, and a Siri with browser mode. These can be seen in FIG. 5AM. Inthe dynamic application mode, the affordances on the touch bar changedepending on the application that is in-focus or currently in use anddisplayed on the primary display, e.g., a mail application will displaymail specific affordances on the touch bar. In the user shortcuts mode,the user can customize the touch bar to include shortcuts. In theworkflows/macros mode the user can create macros each having anaffordance on the touch bar for invoking the workflow or macro. The textentry mode includes affordances related to text entry, like formatting,font size etc. The expanded control strip mode includes expanded systemlevel controls like volume slides, screen brightness controls, etc. Thedefault function keys mode includes affordances for standard keyboardfunction keys, like F1, F2, F3 and so on. The browser+workspaces modeincludes affordances related to browser functionality, and an affordancethat allows a user to easily access their current workspaces.

Some users, however, have found that changing the affordances on thetouch bar, e.g., in dynamic applications control mode, is distracting,and would prefer having a persistent mode for particular applications.For example, when using the mail application, the user may prefer havinga persistent text entry mode displayed on the touch bar instead of adynamic applications control mode. As such, some embodiments allow theuser to assign persistent modes on an application by application basis.FIG. 5AM shows a system preferences touch bar user interface 516 withapplication specific touch bar modes 520, such as a persistent textentry mode 542 of the touch bar assigned to the mail application 540 anda Siri with browser mode 5016 assigned to the web browser application5014. FIG. 5AM also shows the touch bar 104 displaying the text entrymode that includes affordances for changing the font size 568, bold 574,italics 576, and underline 578.

FIGS. 7A-7F flowchart one or more embodiments of a method 700 thatallows users to associate touch bar display modes with variousapplications, in accordance with some embodiments. The method 700 isperformed (702) at a computing system including one or more processors,memory, a first housing including a primary display, and a secondhousing at least partially containing a touch-sensitive secondarydisplay that is distinct from the primary display. Some operations inmethod 700 are, optionally, combined and/or the order of some operationsis, optionally, changed.

In some embodiments, the computing system is portable computing system100 (FIG. 1A) or desktop computing system 200 (FIGS. 2A-2D). In someembodiments, the primary display is primary display 102 (FIG. 1A) whichis implemented in display portion 110 (also referred to herein as afirst housing 110 that includes the primary display 102) of portablecomputing system 100 (FIG. 1A) and the second housing is a body portion120 of the portable computing system 100, and the second housing atleast partially contains the touch-sensitive secondary display (e.g.,dynamic function row 104, FIGS. 1A-1B) and a physical keyboard (e.g.,the set of physical keys 106) (704).

In some embodiments, the second housing is not connected (706) to thefirst housing, e.g., because the first housing is part of a first deviceand the second housing is part of a different device other than thefirst device (e.g., the second housing could be part of a mobile phone,a tablet device, or any other device that includes affordances that aredisplayed on a smaller secondary display while that other device isconnected to a computing system that includes a larger primary display).As one non-limiting example, in some embodiments, the second housing isperipheral keyboard 206 (FIGS. 2A-2B) of desktop computing system 200,which at least partially contains the touch-sensitive secondary display(e.g., dynamic function row 104, FIGS. 2A-2B) and the physical keyboard(e.g., the set of physical keys 106, FIGS. 2A-2B). As another example,in some embodiments, the second housing is first peripheral inputmechanism 212 (FIG. 2C) of desktop computing system 200, which at leastpartially contains the touch-sensitive secondary display (e.g., dynamicfunction row 104, FIG. 2C) and the second housing includes an inputmechanism (e.g., touchpad 108, FIG. 2C) and does not include thephysical keyboard. As one more example, in some embodiments, the secondhousing is part of a wearable computing device (708), such as a smartwatch.

As described below, the method 700 (and associated interfaces) allowsusers to associate touch bar modes with various applications, and todefine which touch bar modes are available system-wide. The examples anddescriptions provided above in reference to method 600 are alsoapplicable to method 700 and, for brevity, those examples anddescriptions are generally not repeated here.

FIGS. 7A-F are flow charts of methods for using or interacting with atouch bar management user interface, such as the touch bar interface 516introduced in FIG. 5A. In particular, FIG. 7 is flow chart of a methodfor allowing users to assign persistent modes on an application byapplication basis. The method is performed at a computing systemcomprising one or more processors, a first housing that includes aprimary display, memory, and a second housing (that is preferablydistinct from the first housing) at least partially containing atouch-sensitive secondary display that is distinct from the primarydisplay and one or more input devices. This computing system isdescribed above with respect to FIGS. 2A-2C. In some embodiments, thesecondary display is a narrow, rectangular OLED display that ispositioned adjacent to a physical keyboard. A suitable secondary displayis Applicant (APPLE INC.'s) Touch Bar. In some embodiments, thesecondary display is any device that includes a smaller display thanthat of the primary display (e.g., the secondary display is a smartwatch).

Initially, a management user interface 516 (see also FIG. 5AG) for thetouch-sensitive secondary display is displayed 702 on the primarydisplay 102. The management user interface includes concurrentlydisplayed representations of a plurality of applications (shown here asA1 and A2, and shown in FIG. 5AG as Mail 540 and Web Browser 5014),including a representation of a first application (e.g., A1 or Mail 540in FIG. 5AG) that, before being displayed within the management userinterface, was associated with one or more display modes of a firstplurality of available display modes for the touch-sensitive secondarydisplay. For example, the available display modes may include a dynamicapplication mode 522, a user shortcuts mode 524, a workflows or macrosmode 526, a text entry mode 528, an expanded control strip mode 530, adefault function keys mode 532, and a browser and workspaces mode 5072,as shown in FIG. 5AG. Also displayed is a representation of a secondapplication (e.g., A2 in FIG. 7A or Web Browser 5014 in FIG. 5AG) that,before being displayed within the management user interface, wasassociated with one or more display modes of a second plurality of theavailable display modes for the touch-sensitive secondary display. Insome embodiments, the first and second plurality of the availabledisplay modes are the same and in other embodiments they are different.In some embodiments, the first and second pluralities of availabledisplay modes may be different if the first or second application isincompatible with some of the available display modes, e.g., if the mailapplication is incompatible with the browser mode. A discussion of theselection of the plurality of available display modes is provided below.

In some embodiments, the management user interface 516 is accessedand/or invoked by navigating to the computing system's settings orsystem preferences to select a user interface element that invokes themanagement user interface for customizing the secondary display. Inother embodiments, the management user interface 516 is accessed and/orinvoked directly from a management user interface affordance on thesecondary display (i.e., touch bar).

Next, it is detected at 706 whether one or more inputs (represented bythe arrow 704) received at the one or more input devices correspond to arequest to modify which of the available display modes is associatedwith the first application (e.g., A1 or Mail 540 in FIG. 5AG). Forexample, the user may select a touch bar display mode to associate withthe A1 (or Mail 540 in FIG. 5AG) application from a pull-down list ofavailable display modes. An example of step 706 is described above inrelation to FIGS. 5E-1 to 5E-3, and 5F to 5G.

At 710, in response to detecting the one or more inputs, the firstapplication (e.g., A1 or Mail 540 in FIG. 5AG) is associated with afirst display mode (e.g., M1 or Text Entry mode 542 in FIG. 5AG) of theavailable display modes, and the management user interface 516 isupdated to indicate that the first application (e.g., A1 or Mail 540 inFIG. 5AG) is associated with the first display mode (e.g., M1 or TextEntry mode 542 in FIG. 5AG) of the available display modes for thetouch-sensitive secondary display. Thereafter, at 714, whenever there isa change in focus at the primary display to a user interface associatedwith the first application (e.g., A1 or Mail 540 in FIG. 5AG), thetouch-sensitive secondary display 104 begins to operate in the firstdisplay mode (e.g., M1 or Text Entry mode 542 in FIG. 5AG), as shown by716.

As described above, in some embodiments, the available display modesinclude an adaptive display mode for the touch-sensitive secondarydisplay, at least one user-defined display mode (e.g., a user may gothrough a customization process in which they are able to select userinterface elements to include on the secondary display in conjunctionwith a particular display mode, and that user-defined display mode maythen be associated through the management user interface with differentapplications), at least one system-defined display mode (e.g., functionkeys), a browser mode, and a workspaces mode (As described in relationto FIGS. 5AS-5AT above). The available display modes include thosedisplay modes that are currently enabled and does not include displaymodes that have been disabled within the management user interface, suchas ones for which an associated checkbox has been un-checked), asdescribed in further detail below.

In prior systems, users were unable to associate available displaycertain modes of a touch-sensitive secondary display with certainapplications displayed on a primary display. Displaying a managementuser interface on the primary display allows a user to predefine anassociation between such secondary display (i.e., touch bar) displaymodes and applications. In some embodiments, detecting an inputselecting a first application and detecting an additional input at arespective option for a first display mode automatically associates thefirst application with the first display mode. Providing this optionenhances operability of the device and makes the human-machine interfacemore efficient (e.g., by allowing the users to predefine an associationbetween a display mode and an application without wasting computingresources during the operation of the application, and thereby allow theusers to easily customize their use of the touch-sensitive secondarydisplay without having to waste time manually searching for desireddisplay mode features that may be difficult to locate).

In some embodiments, the display mode for an application is changedwhile maintaining display of other applications and their selecteddisplay modes. In particular, at 720 (FIG. 7B), the display of therepresentation of the second application (e.g., A2 or Web Browser 5014in FIG. 5AG) is maintained when (i) the request is detected to associatethe first application (e.g., A1 or Mail 540 in FIG. 5AG) with the firstdisplay mode (e.g., M1 or Text Entry mode 542 in FIG. 5AG), and (ii) themanagement user interface is updated, as shown at 722. In this way, theuser is able to remove or change an associated display mode for arespective application while leaving untouched, i.e., maintaining,display of the other application(s) on the list of applications.

Allowing users to modify display modes for a respective applicationwhile continuing to display other applications on the list of one ormore applications helps to ensure that users can make modifications toassociated display modes in a way that requires a small number of inputswhile also ensuring that users are still able to see informationregarding the other applications. This, in turn, helps to enhanceoperability of the device and makes the human-machine interface moreefficient.

In some embodiments, at 724, one or more additional inputs are detected,via the one or more input devices, that correspond to a request tomodify which of the available display modes is associated with thesecond application. For example, an additional input is shown by thearrow 726. In response to detecting the one or more additional inputs,at 728, associating the second application with a second display mode ofthe available display modes, and updating the management user interfaceto indicate that the second application is associated with the seconddisplay mode for the touch-sensitive secondary display. In someembodiments, the second display mode is distinct from the first displaymode, while in other embodiments, they are the same. Thereafter, at 734,a change in focus at the primary display to a user interface associatedwith the second application causes the touch-sensitive secondary displayto begin operating in the second display mode. This is shown, forexample, by 732. The available display modes include the display modesdescribed above.

In some embodiments, the display mode for an application can be changedwhile maintaining display of other applications and their selecteddisplay modes. In particular, as described above for the firstapplication and display mode, at 738 (FIG. 7C) (i) detecting the requestto modify which of the available display modes is associated with thesecond application, (ii) the associating the second application with thesecond display mode, and (iii) updating the management user interface toindicate that the second application is associated with the seconddisplay mode, are all performed while maintaining display of therepresentation of the first application within the management userinterface. In this way, the user is able to remove one of the associateddisplay modes for the respective application while maintaining displayof the other application on the list of applications.

Allowing users to modify display modes for a respective applicationwhile continuing to display other applications on the list of one ormore applications helps to ensure that users can make modifications toassociated display modes in a way that requires a small number of inputswhile also ensuring that users are still able to see informationregarding the other applications. This, in turn, helps to enhanceoperability of the device and make the human-machine interface moreefficient.

In some embodiments, at 742, while the touch-sensitive secondary displayis operating in a display mode (M?) other than the first display mode(e.g., M1) (e.g., an adaptive or persistent display mode), receiving arequest to change focus on the primary display to a user interface forthe first application on the primary display. For example, the requestincludes a user clicking on an affordance on the primary display toinvoke the first application, as shown by the arrow 744, or selecting auser interface associated with the first application but that waspreviously not in-focus on the primary display. In response to receivingthe request, at 746, (i) ceasing to operate the touch-sensitivesecondary display in the display mode (M?) other than the first displaymode and instead operating the touch-sensitive secondary display in thefirst display mode (e.g., M1), and (ii) displaying, on thetouch-sensitive secondary display, user interface elements associatedwith the first display mode (e.g., M1), as depicted by 738.

Ensuring the user-specified associations between applications andsecond-display display modes are maintained as a user opens differentapplications helps to ensure that users are easily able to find the userinterface elements within the secondary display that they would like touse. In this example, ensuring that the secondary display is switched tooperate in the new user-selected display mode, which was specificallyassociated with the particular application, once that particularapplication is open, ensures that the user's preference is followed.This enhances operability of the device and makes the human-machineinterface more efficient (e.g., by ensuring that user's expectations aremet and that they are able to fluidly interact with the secondarydisplay, consistent with their preferences for what should be displayedtherein, as they move between different applications).

In some embodiments, user can enable display modes available forselection. At 750 (FIG. 7D), respective options for enabling ordisabling display modes for the touch-sensitive secondary display aredisplayed within the management user interface on the primary display.For example, the various available secondary display modes describedabove are depicted in a window within the management user interface, asdepicted by 752. This can occur at any time, e.g., before or after anapplication is associated with a particular display mode. In someembodiments, the options (e.g., radio buttons or check-boxes) forenabling or disabling display modes for the touch-sensitive secondarydisplay are displayed adjacent to the list of one or more applications.Reference numeral 752 shows an example where checkboxes are used toallow for a binary choice between enabling or disabling a respectiveoption associated with one of the available display modes. display modesfor the touch-sensitive secondary display, wherein enabling a respectiveoption for a respective display mode of the plurality of display modescauses the respective display mode to be one of the available displaymodes. This is also described in relation to FIGS. 5A-5D.

In some embodiments, the plurality of available display modes describedabove are those display modes for which checkboxes have been selectedwithin a management user interface of the computing system, i.e., thosedisplay modes that have been added to the list of one or more defaultdisplay modes.

Providing users with the option to select one or more display modes toadd to the available display modes for the touch-sensitive secondarydisplay enhances operability of the device and makes the human-machineinterface more efficient (e.g., by allowing the users to add one or moredesired display modes to the available display modes without wastingcomputing resources during the operation of the management userinterface, and thereby allow the users to easily customize their use ofthe management user interface without having to waste time manuallysearching for desired display modes that may be difficult to locate).

In some embodiments, a selection of an additional application to add tothe plurality of applications for which representations are concurrentlydisplayed within the management user interface is received at 754. Forexample, the selection may include the user selecting an “+” button 756,and, in response, a menu of applications is then displayed to allow theuser to choose additional applications to add to the list of one or moreapplications. In response to receiving the selection, a representationof the additional application with an indication that the additionalapplication is associated with one of the available display modes forthe touch-sensitive secondary display is displayed 758 within themanagement user interface. In some embodiments, the selection causes theadditional application to be immediately added to the list of one ormore applications and one of the multiple available display modes is bydefault associated with the additional application. A user is then ableto choose a display mode (e.g., M3) of the multiple available displaymodes to associate with the additional application (e.g., by selectingone of the up or down arrow keys shown in FIG. 7D to scroll through themultiple available display modes). Reference numeral 760 shows theaddition of a third application (A3) and third display mode (M3).

In some instances, within the management user interface, users areunable to associate an application with a display mode because theapplication does not appear within the management user interface.Providing the user with the option to select one or more additionalapplications to include in the management user interface enhancesoperability of the device and makes the human-machine interface moreefficient (e.g., by allowing the users to add a desired application tothe management user interface without wasting computing resources duringthe operation of the management user interface, and thereby allow theusers to easily customize their use of the management user interfacewithout having to waste time manually searching for desired applicationsthat may be difficult to locate).

In some embodiments, the touch-sensitive secondary display has one ormore default display modes, and each application of the plurality ofapplications for which a representation is displayed within themanagement user interface is associated with a respective user-selecteddisplay mode that is distinct from the default display mode(s).

In some embodiments, the one or more default display modes includes anadaptive display mode. In some embodiments, the one or more defaultdisplay modes are each activated or de-activated (e.g., using a checkboxor radio button) by a user within the management user interface. Forexample, as shown by reference numerals 750 and 752 in FIG. 7D, a useris able to select any of the checkboxes to activate or de-activateavailable default display modes for the touch-sensitive secondarydisplay. In some embodiments, at 764 (FIG. 7E), a respective applicationon the list of one or more applications may be associated with thedefault display mode for the touch-sensitive secondary display, and therespective application must also be associated with some other displaymode (e.g., a user-defined display mode that is specific to therespective application) in order for that respective application to alsobe displayed in the list of one or more applications in the managementuser interface). In some embodiments, the default mode includes aplurality of available display modes for the secondary display, whilethe other display mode is a particular one of the plurality of availabledisplay modes that is persistently associated with a particularapplication until the user changes it or removes the particularapplication from the list.

In conventional systems, users were unable to associate a firstapplication with a single display mode of a plurality of availabledisplay modes instead of being permanently assigned to the one or moredefault display modes. Providing the user with the option to associatethe first application with a particular display mode of the availabledisplay modes and not the default display mode(s) enhances operabilityof the device and makes the human-machine interface more efficient(e.g., by allowing the users to predefine an association between adisplay mode and an application without wasting computing resourcesduring the operation of the application, and thereby allow the users toeasily customize their use of the touch-sensitive secondary displaywithout having to waste time manually searching for desired display modefeatures that may be difficult to locate).

In some embodiments, displaying the management user interface for thetouch-sensitive secondary display comprises displaying 766 each of theconcurrently displayed representations for the plurality of applications(e.g., A1, A2, A3) concurrently with displaying information regardingrespective user-selected display modes (e.g., M1, M2, M3) for thetouch-sensitive secondary display associated with each of the pluralityof applications. In some embodiments, each application and itsassociated display mode is aligned in a row or column.

In conventional systems, the user is unable to view and manipulate thelist of one or more applications and their corresponding indications ofone or more display modes simultaneously because they are displayed ondifferent screens, at different times, and/or in different locations.Displaying the list of one or more applications concurrently whiledisplaying the corresponding indications of the respective one or moredisplay modes enhances operability of the device and makes thehuman-machine interface more efficient (e.g., by allowing the users toview and manipulate the one or more applications and their correspondingdisplay modes simultaneously, and thereby allow the users to efficientlynavigate within the management user interface without having to wastetime manually switching between separate user interfaces).

In some embodiments, at 770 (FIG. 7F), the available display modesinclude at least one user-defined display mode 772 created by a user ofthe computing system. The user-defined display mode is a display modefor the secondary display that a user can create or customize. In someembodiments, the user is able to select a button within the managementuser interface to initiate a process that invokes a process for creatinga new touch bar display mode. An example of a user selecting a “createtouch bar mode affordance” 534 my moving an arrow 5018 over theaffordance and selecting it, is shown in FIG. 5V. FIGS. 5W-5AF show anexample of the process for creating a new touch bar display mode.

Returning to FIG. 7F, in some embodiments, the available display modesinclude 774 at least one system-defined display mode that was notcreated by a user of the computing system. For example, thesystem-defined display mode may be a function row 776 having functionkeys F1, F2, F3, etc.

In some embodiments, disabling 778 a respective option (e.g., byunchecking 780 a check-box) for a respective display mode of theplurality of display modes causes the respective display mode to beremoved from the available display modes. For example, removing adisplay mode from the available display modes prevents the respectivemode of operation from being enabled for applications on the device(e.g., applications can no longer be associated with the removed displaymode), and also removes the respective mode of operation from anyapplications for which the respective mode of operation was previouslyenabled).

It should be understood that the particular order in which theoperations in FIGS. 7A-7C have been described is merely one example andis not intended to indicate that the described order is the only orderin which the operations could be performed. One of ordinary skill in theart would recognize various ways to reorder the operations describedherein.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best use the invention and variousdescribed embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method, comprising: at a computing systemcomprising one or more processors, a first housing that includes aprimary display, memory, and a second housing at least partiallycontaining a touch-sensitive secondary display that is distinct from theprimary display and one or more input devices: displaying, at thetouch-sensitive secondary display, at least a system-level affordancefor controlling a system-level feature and an affordance for causingdisplay of representations of user-defined workspaces at thetouch-sensitive secondary display; receiving a first input at theaffordance for causing display of the representations the user-definedworkspaces; in response to receiving the first input, displaying, at thetouch-sensitive secondary display, a selectable user interface objectcorresponding to a first window from a first application and a secondwindow from a second application; receiving a selection, via a secondinput, corresponding to selection of the selectable user interfaceobject corresponding to the first window from the first application andthe second window from the second application; in response to receivingthe second input corresponding to selection of the selectable userinterface object corresponding to the first window from the firstapplication and the second window from the second application,displaying the first window from the first application and the secondwindow from the second application.
 2. The method of claim 1, including:in response to receiving the first input, displaying, at thetouch-sensitive secondary display, another selectable user interfaceobject corresponding to a third window from a third application and afourth window from a fourth application.
 3. The method of claim 1,wherein displaying the first window from the first application comprisesdisplaying the first window f on the primary display.
 4. The method ofclaim 1, wherein displaying the first window from the first applicationcomprises displaying the first window on the primary display, andwherein displaying the second window from the second applicationcomprises displaying the second window f on the primary display.
 5. Themethod of claim 1, including: in response to receiving the second inputcorresponding to selection of the selectable user interface objectcorresponding to the first window from the first application and thesecond window from the second application, ceasing to display theselectable user interface object.
 6. The method of claim 5, including:in response to receiving the first or second inputs, ceasing to displaythe system-level affordance.
 7. The method of claim 1, including: beforereceiving the first input, displaying, at the primary display, anotheruser interface associated with an application; and in response toreceiving the second input, ceasing to display the user interfaceassociated with the application.
 8. The method of claim 1, wherein thesecond housing includes a keyboard and a trackpad, wherein the trackpadis distinct and separate from the touch-sensitive secondary display. 9.The method of claim 8, wherein the keyboard and trackpad are locatedfarther away from the primary display than the touch-sensitive secondarydisplay while the computing system is an opened state.
 10. The method ofclaim 1, wherein the selectable user interface object includes arespective thumbnail that previews the first window from the firstapplication and the second window from the second application
 11. Themethod of claim 1, wherein the primary display is a touch-sensitivedisplay.
 12. An electronic device, comprising: one or more processors; afirst housing that includes a primary display; a second housing at leastpartially containing a touch-sensitive secondary display distinct fromthe primary display; and memory storing one or more programs that areconfigured for execution by the one or more processors, the one or moreprograms including instructions for: displaying, at the touch-sensitivesecondary display, at least a system-level affordance for controlling asystem-level feature and an affordance for causing display ofrepresentations of user-defined workspaces at the touch-sensitivesecondary display; receiving a first input at the affordance for causingdisplay of the representations the user-defined workspaces; in responseto receiving the first input, displaying, at the touch-sensitivesecondary display, a selectable user interface object corresponding to afirst window from a first application and a second window from a secondapplication; receiving a selection, via a second input, corresponding toselection of the selectable user interface object corresponding to thefirst window from the first application and the second window from thesecond application; in response to receiving the second inputcorresponding to selection of the selectable user interface objectcorresponding to the first window from the first application and thesecond window from the second application, displaying the first windowfrom the first application and the second window from the secondapplication.
 13. A non-transitory computer-readable storage mediumstoring executable instructions that, when executed by one or moreprocessors of a computing system with a first housing that includes aprimary display and a second housing at least partially containing atouch-sensitive secondary display distinct from the primary display,cause the computing system to: display, at the touch-sensitive secondarydisplay, at least a system-level affordance for controlling asystem-level feature and an affordance for causing display ofrepresentations of user-defined workspaces at the touch-sensitivesecondary display; receive a first input at the affordance for causingdisplay of the representations the user-defined workspaces; in responseto receiving the first input, display, at the touch-sensitive secondarydisplay, a selectable user interface object corresponding to a firstwindow from a first application and a second window from a secondapplication; receive a selection, via a second input, corresponding toselection of the selectable user interface object corresponding to thefirst window from the first application and the second window from thesecond application; in response to receiving the second inputcorresponding to selection of the selectable user interface objectcorresponding to the first window from the first application and thesecond window from the second application, display the first window fromthe first application and the second window from the second application.